{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":28488,"path":"it-business-management/test-management/run-your-test-assignments.md","title":"Run your test assignments in Test Management 2.0","bundle":null,"doc_type":null,"release":"australia","body":"\n# Run your test assignments in Test Management 2.0\n\nRun your test assignments and capture the results.\n\n## Before you begin\n\nBefore you begin, ensure the following conditions are met:\n\n-   Your test manager has set the tests to **Ready** state and assigned them to you.\n-   At least one execution environment is configured in your instance.\n\nRole required: sn\\_test\\_management.tester\n\n## Procedure\n\n1.  Navigate to **All** &gt; **Test Management 2.0** &gt; **Tests Assigned to me**.\n\n2.  Select the required tests and click **Run**.\n\n    Only the tests that are in the Ready state can be run.\n\n    If no tests appear in the **Tests Assigned to me** list, confirm with your test manager that tests have been assigned to you and set to **Ready** state.\n\n3.  In the pop-up, select the execution environment on which the tests must be run.\n\n    An execution environment specifies the hardware or software configuration on which tests run, such as a browser version or operating system. If no environments appear in the list, contact your system administrator to configure one.\n\n4.  In the Test Execution pop-up, mark a step as passed, failed, or blocked using the following icons.\n\n<table id=\"choicetable_p33_dsw_dcb\"><thead><tr><th align=\"left\" id=\"d309033e123\">\n\nIcon\n\n</th><th align=\"left\" id=\"d309033e126\">\n\nDescription\n\n</th></tr></thead><tbody><tr><td id=\"d309033e132\">\n\n**\\[Omitted image \"passedtest.png\"\\] Alt text: Icon to indicate a step as passed**\n\n</td><td>\n\nPassed.\n\n</td></tr><tr><td id=\"d309033e147\">\n\n**\\[Omitted image \"failedtest.png\"\\] Alt text: Icon to indicate a step as failed**\n\n</td><td>\n\nFailed. In this state, options to add comments and attachments are available. **Note:**\n\nTo log a defect in Test Management 2.0, create a defect record manually and include the test name and step number in the defect description.\n\n</td></tr><tr><td id=\"d309033e171\">\n\n**\\[Omitted image \"blockedtest.png\"\\] Alt text: Icon to indicate a step as blocked**\n\n</td><td>\n\nBlocked. In this state options to add comments and attachments are available.\n\n</td></tr></tbody>\n</table>    To pause and work on the test at a later point in time, click **Pause**.\n\n5.  Click **Done**.\n\n\n## Result\n\nTest results are saved to the Test Result form. The overall status of the test is defined by statuses of the test steps:\n\n-   If all the test steps are passed, the status of the test is **Passed**.\n-   If at least one step of the test is not run, 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\nTo view the full history of test runs and results across all test plans, navigate to **Test Management 2.0** &gt; **Test Runs**. For more information about monitoring test plan progress, see [Test Board in Test Management 2.0](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-business-management/test-management/test-board.md).\n\n**Parent Topic:**[Testing using Test Management 2.0](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-business-management/test-management/release-readiness-testing.md)\n\n**Related topics**  \n\n\n[Create a test in Test Management 2.0]()\n\n[Create a test set in Test Management 2.0]()\n\n[Test Board in Test Management 2.0]()\n\n[Create a test execution suite in Test Management 2.0]()\n\n"}}