Feature Requests

qase.step in Jest/Vitest (and probably other packages too) sets Action field only, so having the other 2 fields as they exist in Qase dashboard would be great.

We want to be able to modify the result status without having to retest the case; if an incorrect result was submitted accidentally, we have to go through the trouble of re-performing the entire case again. It can be either a setting or a role permission.

Add a field to capture persistent comments across test cases quickly. Right now, I want to quickly note down some observations about a test while running it. The options I have are, either I add it as a comment in the result, which means, it'll only be good for that particular result. Or, I have to open the test case in a new tab and add it a custom field / case's description. This makes it persist, but it's tedious to have to do it for every test case, not to mention the constant switching of context for each case.

Test run result marks as failed in case if one of test cases has result - failed, blocked, invalid, but it can be normal for the test run and not to use the skipped option or mute option which applies not only to the current test run but to the test case.

It will be convenient to have a Project setting for the test runs which will allow to automatically mark all steps of a case Passed, if a case itself got marked passed.

Currently, the mouseover on the chart only shows the count (e.g., “Retest: 6”). Please add an option to also display the percentage in the tooltip. For example, show “Retest: 6 (13%)” when the value is 6 out of 45. This should help users quickly understand the data distribution without manual calculation.

When executing a test, it'd be nice to see the view in Classic view, similar to when creating the test script. Classic view: three columns: [action] [data] [expected result]

Implement case assignment stories in the test run of changes to the test run so that it is possible to roll back.

I may not know the exact day or time when I will run the test within the next month — scheduling a test run for a specific date or time is not feasible in this case. In such situations, it would be helpful to allow users to mark test runs with a "To Do" status, rather than setting them to "In Progress" by default. Otherwise, stakeholders reviewing the list of test runs showing 0% progress might be confused about why no progress is being made. Introducing a "To Do" status would help eliminate this confusion.

Currently when starting test run the selection of test cases can be filtered by many things but not by "Assigned To". This will be very helpful when selecting test cases in test runs in order to select specific cases, and not to select all and then exclude cases.