Default test runs workflow
The test runs workflow defines the path a test run takes from the time it is created to completion. Test runs are assigned to users who follow the steps in the test run to perform the test. When the work is complete, the user enters an event to move the test run to the next state in the workflow. The test run Status field indicates the current state and assignment.
You can use the default test runs workflow out of the box or customize it to support your process. The default workflow includes the following events.
Event | Use to: |
---|---|
Assign | Assign test runs to users. For example, you need to assign a test run to a tester to perform the test or a tester may need to assign a test run to the QA manger if experiencing problems during the test. |
Estimate | Estimate the time needed to perform tests. Typically, a project manager or QA team lead enters the estimated effort before assigning test runs. After the estimate is entered, you can track the time it should take to complete a task. |
Start | Start test runs when they are ready for testing. |
Enter Work | Enter work you complete on test runs to keep others informed about your progress. |
Enter Result | Enter overall test results after you complete test runs. |
Pass | Pass and close test runs without entering additional results information. |
Fail | Fail and close test runs without entering additional results information. |
Unclear | Indicate the test results are not clear and need to be reviewed without entering additional results information. |
Hold | Place test runs on hold so additional work can be completed before they are performed. For example, you may want to put a test run on hold if the required test environment is not available. |
Resume | Resume on hold test runs. |
Re-Open | Reopen closed test runs if you need to make changes or run tests again. |
Ignore Result | Ignore results for Passed, Failed, or Unclear test runs to close them. Helps you exclude test runs when you view results based on workflow state in filters, reports, and other areas. For example, after you regenerate failed test runs, add this event to move the original test runs from the Failed state to the Closed (Ignored) state to determine which failed test runs need to be retested. |
Comment | Add comments to test runs to clarify information or add notes for other users. |
Note: To add workflow events to test runs, choose an option from the Workflow menu