Feature Requests

Hello everyone! I have "update" webhook that trigger my endpoint with custom handling of updated test case. In short, I request details of test case (by ID from webhook request body) to get its custom fields and check each custom field by custom logic. So now I need to do the same actions with deleted test cases but API doesn't provide the ability to get details of deleted test cases. Is it possible to add functionality which allow me to get details of the deleted case?

please add "update" endpoint for test-run to allow the following: update the description. add comment to test-run.

Using the data from the Playwright run, Qase should automatically mark the status for flaky test results as flaky. Since the 'Flaky' status is already available from Playwright (a test is categorized as flaky if it failed on the first run, but passed when retried), it would be great to see this carried forward in Qase. Manually marking test cases as flaky is cumbersome, and ideally it would be better to mark it flaky at the run level. It would also be amazing to see a 'Flaky tests' dashboard widget, that lists the flaky test cases in the past x days (similar to the 'Flaky test cases count' dashboard, but instead of count, list the test names)

Hi, We have a custom integration that leverage the API capabilities. This works great so far. As part of our framework, we added a coverage report at the end of the run. However, the API currently doesn't support adding attachments nor comment at the run level, preventing us to add the coverage report at the run completion. After a chat with the support, it appears to be something that currently doesn't have a known workaround (In Qase.io ). Would that be a feature that may be considered in the future? Nicolas ------- PS: A little more on the need. Here, the context is only Rest API testing and CI automated. We are currently using a custom integration (It's Jest underneath, but results are sent through the Qase API using a custom reporter, which allow us to add far more details that the standard integration). At the end of the run execution, we generate an API coverage report that follow this approach >> https://personal.us.es/amarlop/wp-content/uploads/2019/09/Test_Coverage_Criteria_for_RESTful_Web_APIs.pdf <<. In search of a solution we opted for a relatively simple "file" generation, hence this request. However the actual need is to have "coverage reporting" capabilities for our Rest APIs. And so any other option that can fit this need would make it, perhaps even better if this is native Qase UX/UI rather than an exported/attached file :-).

When running tests in parallel, Qase does not calculate the execution time correctly. Since it adds up each test's duration, it treats the test run like it ran sequentially. This makes it seem like the tests took a lot longer than it really did, and reports an incorrect execution time.

Scenario: I’m running an end-to-end (E2E) test with Playwright configured as follows: • Browser: Chrome • Theme: Dark mode • App Version: Android Currently, there is no option to set these configuration parameters directly in the reporter options. As a result, users must manually edit these settings through the UI after the test run. Suggestion: Implement a feature that allows users to start a test run with predefined configuration options. If these configurations do not already exist, the system should automatically create them and link them to the test run.

Currently, new test cases automatically created by a reporter app are marked with the ‘isManual’ property. Reporters use the ‘create-result’ endpoint to publish results to Qase. If a test case ID is not specified, the endpoint also creates the test case. However, this endpoint’s parameters do not include an option to set the ‘Automation status’ value. As a result, users must manually change the property of these newly created cases to ‘Automated’ from the UI, which adds an unnecessary step.​

When creating a test run, add a field for browser

The case is reported when viewing the Defects page but not in the Defects API response.

We can now link results and runs to 3rd party issue trackers, however this is not possible via API. GET https://app.qase.io/apps/api/{external_name}/issues/search?query={external_issue} This call to get the possible external issue details, specifically it's ID POST url = "https://app.qase.io/v1/run/{project}/external-issue/{run_id}" payload = {"external_issue":{"external_id":{external_id}","slug":"{external_name}","display_name":"{display_name}","link":"{link}"}} However the response is: GET {'error': 'Unauthenticated.'} POST {'message': 'CSRF token mismatch.'} I wanted to be able to link several runs to a single external issue tracker issue however I'm unable to do so with the current state of the API. I now need to manually link each run to the external issue. Not terrible but not great either.