{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":26396,"path":"it-business-management/agile-development/run-test-plan-within-agile.md","title":"Run tests for a story in Agile Development 2.0","bundle":null,"doc_type":null,"release":"australia","body":"\n# Run tests for a story in Agile Development 2.0\n\nFor a story whose tests are marked ready to be run, run those tests and execute all the test steps. Do this using the Sprint Tracking tab of the Agile board in Agile Development 2.0.\n\n## Before you begin\n\nRole required: scrum\\_user\n\n## About this task\n\nFrom the Agile board, use the List view of the Sprint Tracking tab to check stories that have test versions ready to be run. These stories have a **Run** option next to their state. Run those tests by executing and verifying each test step.\n\n## Procedure\n\n1.  Navigate to **All** &gt; **Agile Development** &gt; **Agile Board**.\n\n2.  From the Sprint Tracking tab, select the **List**view.\n\n    All stories scheduled for the current sprint are listed as sections, which can be expanded and collapsed.\n\n3.  From the **Show** field, select **Tests**\n\n4.  For the story that you want to run the tests on, select **Run**.\n\n5.  Select the environment on which the test is to be run and confirm by selecting **Run**.\n\n6.  In the Test Execution window, execute each test step and mark them as passed, failed, or blocked accordingly.\n\n    -   Passed \\(\\[Omitted image \"passedtest.png\"\\] Alt text: Step passed icon\\)\n    -   Failed \\(\\[Omitted image \"failedtest.png\"\\] Alt text: Step failed icon\\)\n    -   Blocked \\(\\[Omitted image \"blockedtest.png\"\\] Alt text: Step blocked icon\\)\n    If you select Failed or Blocked for a test step, you can enter comments and attach files to support your selection.\n\n7.  If you're running multiple tests for the story, use the Next Test option \\(\\[Omitted image \"icon-next-test.png\"\\] Alt text: Next test icon\\) to move to the next test after verifying the current one.\n\n8.  Repeat step 6 and 7 until you've executed and verified all the test steps.\n\n9.  You can pause the test for the moment by selecting **Pause**\n\n    If you've paused the test, skip step 10.\n\n    When you want to resume the paused test run later, you can find it at **Test Management** &gt; **Runs**.\n\n10. After marking all test steps, select **Done**.\n\n\n## Result\n\nThe result of each test is indicated on the Agile board as Passed, Failed, Blocked, or Not finished according to the following conditions.\n\n-   If all the test steps are passed, the status is **Passed**.\n-   If at least one step of the test is not executed, the status of the test is **Not finished**.\n-   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.\n-   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.\n\n## What to do next\n\n[View the test results for a story in Agile Development 2.0](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-business-management/agile-development/view-test-result-form.md)\n\n**Parent Topic:**[Managing your product development using Agile Development 2.0](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-business-management/agile-development/using-agile-development-2-0.md)\n\n"}}