Qase Roadmap

Currently, test steps are only displayed in reports once a test has been executed. This limitation makes it difficult to share pre-execution plans with stakeholders, especially when they have read-only access. Test steps are a critical part of test case design and planning, and visibility into these steps is often needed before execution. Expected outcome: When generating or sharing reports, test steps should be visible regardless of whether the tests have been executed. This ensures that: Stakeholders can review the planned steps in advance. Read-only users can access detailed information about test case steps without requiring additional documentation. The report serves as a comprehensive reference for both planning and execution.

I identify that several requests have been made so that the states of the defects and their process as such can be edited but it is still not taken into account, I also leave my request since the default states do not work the same for all of us, I appreciate you taking this into account and could be edited according to the needs of the users

After resolving a defect, an option to set all the related test cases in test runs to Re-test would be very useful.

When I run my automated test suite via Robot Framework, the pass/fail results are sent to a test run in Qase. It would be extremely beneficial if I was able to also attach the automation report (includes detailed steps and screenshots).

Use Case: There are 40+ test cases that all need the same shared step added to them. Current Behavior: User must navigate into each test case and add the shared step, which takes no less than 4 mouse clicks and has the potential to be more if the user accidentally clicks on "add step" instead of "add shared step" Proposed Behavior: Allow bulk edit of test case shared steps so the user can add the same shared step to all 40+ test cases at once.

Shared steps are very useful and i propose will be a lot more if we could parameterize them. For a piece of data thats required in the shared step can be named as a variable/parameter which can be specified a value either in the test case or during test run time. This will make the shared steps way more reusable and us QA Engineers a lot more productive.

It would be great to have an option to use shared steps not in just one project, but choose multiple projects to use it in.

The notification sent by QASE to the specified Slack channel indicates that the test has failed, but the Slack message is still showing in green instead of red.

As a QA Manager or Test Lead, it’s crucial to identify defects that have been observed across multiple test runs to highlight recurring issues that need attention. This allows stakeholders to assess the impact and decide on the priority of fixing these defects.

Up to now the TCs IDs was visible in test reports.