Run your tests from the List view
On this page
Run your tests from the List view
View the test scenario, execute all the steps of the test, and review the test result.
Before you begin
Role required: scrum_user
Procedure
-
Navigate to All > Agile Development > Agile Board.
-
Click the Sprint Tracking tab and select the List view.
-
Click a test.
-
Verify a story by clicking Run on the story.
This step runs all tests of the story at once.
-
In the pop-up, select the environment on which the test is to be run.
-
Click Lookup using list icon.
-
Click Run.
-
-
In the Test Execution pop-up, mark a step as passed, failed, or blocked using the following icons.
Icon Description [Omitted image “passedtest.png”] Alt text: Step passed icon Passed. [Omitted image “failedtest.png”] Alt text: Step failed icon Failed. In this state, options to add comments and attachments are available. Option to delete attachments is also available. [Omitted image “blockedtest.png”] Alt text: Step blocked icon Blocked. In this state, options to add comments and attachments are available. Option to delete attachments is also available.-
To select an icon, you can also use the Tab key. Press Tab and then press Enter.
-
To pause and work on the test at a later point in time, click Pause.
-
-
Click Done.
Result
Test result is saved to the Test Result form, and the latest test result of each test is displayed in the List view.
The overall status of the test is defined by statuses of the test steps:
-
If all the test steps are passed, the status of the test is Passed.
-
If at least one step of the test is not run, the status of the test is Not finished.
-
If at least one step of the test fails, the overall status of the test is Failed. This rule takes precedence over the previous rule.
-
If at least one step of the test is blocked, the overall status of the test is Blocked. This rule takes precedence over the previous two rules.
Parent Topic:Sprint testing
Related topics
{Create a test for a story}[]
Keep exploring.
Find another answer, or bring this documentation into your own tools.