Feature Requests

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.

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)

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.

Some of the end to end automation test cases in robot file map to multiple qase test ids, Currently qase-robotframework reporter does not support passing multiple qase ids to be passed in the robot test cases tags.

It would be cool to integrate with Redmine to create custom reports.

The situation is the following: 1) I have test case ABC-123 in qase.io . 2) I have integrated Cypress with Qase 3) I have a test spec file with 3 tests in Cypress 4) All those 3 tests are related to ABC-123 test-case The thing is, that when running this single spec file with qase-reporter, and I make one test (one "it" block ) to fail, I see that the test-run is passed in Qase.io with that single ABC-123. Feature Request: I think, it is more than logical to fail the test-run/case in qase.io , if one of the related automated tests is failed. Also provide an informative UI to easily understand which one is failed and passed.