It will be useful to have a possibility to disable certain statuses when performing a test run, i.e. an engineer can only pass or fail cases, but not skip them.

There needs to be an ability to specify more precisely what the failure was caused by during the test run, which can then be used in reporting.

For example: a failure can be caused by network issue, config issue, test case code - and it's not a real "defect" per se.

Furthermore, when such data exists, it will be beneficial to use it in the reporting: for example, a pie chart that shows a breakdown of failures by category.

I have some TC which I wants to marked them as Deferred but there is no option

Allow admin user to create a variety of Pass/Fail/Soft Fail/Bug etc etc statuses that suit the business requirements. Rather than be restricted to the fixed set of statuses in Qase.

These statuses will help the workflow and integration with other departments, where the standard pass/fail/blocked/invalid/skipped are insufficient.

The statuses, once set, would be available for all test runs (not configurable per run).

This suggestion may have already been raised but i cannot find one similar.

When doing a test run, it would be great to have the option to set the status to "In Progress" on a test case. This will help for big test cases where you need to pause and come back later and will also give a good overview on the Dashboard of what is currently being worked on.

Some TMSs have one more status for run, named like "bugs" with yellow color.

This means, that this exact TC passed, but some bugs were found during the TC.

This is not so important feature, of course. But unfortunatelly only one status confuses our testers, because they don't know wether they have to fail TC or not.

I want to add a custom result of retest.