Is there an easier way to re-test?
We are using Zephyr Scale on Cloud and have a whole bunch of Test Cases set up in a Test Cycle for a large-scale system regression test. I'm looking for if there is a better way to create new executions of a test than having to send someone all the way back to the Test Cycle to find a test in the player.
Here's our current workflow:
- Tester uses the test cycle player to work through their assigned tests
- If they find a defect they fail the test and use the gear icon to add a new work item creating a related Defect ticket. This then nicely links the Defect to the failed execution.
The issue comes with when the defect is reported resolved and we want to re-run the test case.
What we would like is for the reporter of the defect to be able to easily run a new execution of the referenced test case so that history is preserved that it did fail and then it passed.
However, clicking on the linked test execution from the Defect ticket takes you to the specific execution by itself. We are seeing people just updating the status to "Pass", which on some level works but loses all history.
We are telling folks to go back to the test cycle, then find the specific test (that they have to remember) and then click "Start New Test Execution" and then Pass it.
Is there any way to get a new execution of a test within the cycle context directly from a linked issue?
Or are we using this in an unintended way?
All of our reporting for this project is being driven by the test cycle, so it is really important to have passes be in the context of the cycle.