Feature Requests

The Suite Description is not needed to be visible for the whole test run. And since the font and size are the same as the Pre and Post conditions of the respective cases, this could be confising and result in missing the instructions inside the pre-condition by the tester.

The Suite Description is not needed to be visible for the whole test run. And since the font and size are the same as the Pre and Post conditions of the respective cases, this could be confising and result in missing the instructions inside the pre-condition by the tester.

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.

Given execution on a Test Case in a Test Run has been started When a final status has not been marked Then the Test Run will show that the test case execution status as "In Progress" or "In Process" This would be beneficial for multiple reasons - more accurate reflection of run progress, letting everyone know what cases have been started but not completed, etc. Sometimes we execute test cases that require multiple days to finish - it would be nice to be able to see at a glance which of these test cases have been started but not finished (maybe the steps for the data staging, initiation of the transaction has started but the end result has not yet had time to be processed and documented)

Test suite name in qase should not be bind with robot file name. This can be passed as QAse parameter also. so that same robot file can be run with different parameter. otherwise same test case will be over written while executing in different config. but ideally it should be reported seprately.

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 would be helpful to have possibility to search and filter test cases by parameters in test run. For example, I have test cases with parameter "internet" and values "slow, fast, offline". In test run I would like to have opportunity to find all cases with parameter "internet" and specific value - "slow"

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.

It would be helpful to see how much time has elapsed while viewing the case opened in run wizard. At the moment, the recorded time can only be seen upon submitting a result, or after the result is submitted.

Although is not exactly a result, it would be great to be able to leave a comment upon submitting a "skipped" result - in such cases when we are not planning to go back to "skipped" cases due to logic of the run execution, seeing the reason for case being skipped in a comment will be helpful.