In addition to the necessary bug fixes, this release includes the following functional changes to Testersuite:
Test cases with blocking defects longer appear in the "Tests to Run" task
When a tester runs the "Tests to Run" taskand defect a blocking defect for a test case, testing cannot continue in that test run. As a result, the test case continued to appear in the "Tests to Run" task for the tester until the defect could be defect . As a result, testers thought a test was ready for them, even though it was not executable.
This has now been updated, so that a test case with a blocking defect longer "counts" toward the task. As soon as the blocking defect "Retest," the task reappears for the tester. The tester can then retest the test step, which allows the blocking defect to be defect .
Test run details can be modified while the test run is in progress
Once a test run was initiated, it was locked against changes. Users with the role of test coordinator or higher could still make changes via an “unlock” button within the test run if necessary. Because you couldn’t see which test runs were locked against changes in the list of test runs, this caused frustration among test coordinators when they wanted to make (bulk) changes to a locked test run.
Starting with this release, test coordinators can make changes to test runs while they are in progress. If these changes affect a test that is currently running, the tester will automatically receive a clear notification about the change, after which the test run will be refreshed. This ensures that it is always up to date.