---
sourceDocument: Yokohama Build or modify applications
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/application-development

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Run an automated test

# Run an automated test {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

After creating an automated test, run it on a non-production instance.

## Before you begin

You must have created the test you want to run.  
The [test
execution property](https://servicenow-prod.fluidtopics.net/kcx6hsY5387sFbfeJbFwlw "On the Properties form, you can set parameters that control how the system executes automated tests and test suites.") must be enabled. You must have an admin or atf_test_admin role to do so.  
Note:  
The test execution property is disabled by default to prevent running tests on a production system. Run tests only on development, test, and other sub-production instances.

Role required: atf_test_admin, atf_test_designer, or
admin

## Procedure

1. Navigate to AllAutomated Test FrameworkTests.
2. If necessary to view the tests list, click Tests.
3. Click the row containing the test that you want to run.  
   The system displays the Test form.
4. Click Run Test.  
   Note:  
   If the test execution property is not enabled, the Run Test button does not appear. In this case, see the annotation at the top of the form, and click the link to enable running tests.

   If the test includes a form step (any step involving a UI), or other kinds of [UI test steps](https://servicenow-prod.fluidtopics.net/8Z9mdUYgpKuwgMSKFSb9~Q "Test user interfaces by mimicking user actions and interacting with the visible components of a page."), the [Pick a browser](https://servicenow-prod.fluidtopics.net/MowfYHt0cQxkNUHtEOESRQ "If the test or test suite you are running contains steps that work with a form (any step involving a UI), or any other UI test step element (such as Automated Service Catalog test steps), work with the Pick a Browser dialog.") dialog appears before executing the tests. Use it to choose among any currently running test clients, or start a new runner. For more information, review [Browser recommendations for all tests and suites](https://servicenow-prod.fluidtopics.net/RCkgkemnippD_sUkq2mTnw#atf-test-runners__kvv_h25_gx). If the test only includes [server test steps](https://servicenow-prod.fluidtopics.net/EaJztQr1sv02IzB3LQOKqg "Test business logic and background processes by performing operations on the server."), the system executes the tests without displaying the Pick a Browser dialog.

## What to do next

Monitor the progress of the test in the Run Test progress dialog. When complete, click Go to Results (on the Run Test progress dialog) to display the Test Results list, where you can [view and analyze test results.](https://servicenow-prod.fluidtopics.net/jOP_IjQnL4z160_g2940~Q "View test results from completed test and test suite runs. Carefully consider the results of automated test runs and perform any corrective actions required to resolve any revealed issues.")  
Note:  
If your test creates data, the system rolls back that data after all steps in the test complete.
**Related concepts**   

* [Cancelling automated tests and test suites](https://servicenow-prod.fluidtopics.net/7QK4cItQGt5TOq9Wd2ewqA#atf-cancelling "You can cancel automated tests and automated test suites that are running or are queued to run.")

*[\>]: and then