---
sourceDocument: Australia Build or modify applications
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/application-development

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Run an automated test suite

# Run an automated test suite {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 min. de leitura

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

## Antes de Iniciar

You must have created the test suite you want to run.  
The [test
execution property](https://servicenow-prod.fluidtopics.net/ETWjnPZvh~S1mvaNdoH6RA "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.  
Nota:  
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

## Por Que e Quando Desempenhar Esta Tarefa

This procedure outlines how to start a test suite manually. You can also schedule test suites to run at a later time. For more information, see [Working with scheduled test suites](https://servicenow-prod.fluidtopics.net/fBJ0JOZHXPAA_HUniq2V6g#atf-sched-suites "You can schedule a test suite to run at a specified date and time.").

## Procedimento

1. Navigate to AllAutomated Test FrameworkSuites.
2. If necessary to view the Test Suites list, click Test Suites.
3. Click the row containing the test suite you want to run.  
   The system displays the [Test
   Suite](https://servicenow-prod.fluidtopics.net/~5TN8tqB2hSR4s9WT300OA "The Test Suite form contains information about one test suite.") form.
4. Click Run Test Suite.  
   Nota:  
   If the test execution property is not enabled, the Run Suite 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 tests associated with the test suite include a form step (any step involving a UI), or other kinds of [UI test steps](https://servicenow-prod.fluidtopics.net/gUn1RNkppvW9PqgWCX0r_A "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/0P82AoQnAzSGeuu36oROxw "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.
5. 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/Y5T3GNxDXHfg8_tFtYF9Qw#atf-test-runners__kvv_h25_gx).  
   If the tests associated with the test suite only include [server test steps](https://servicenow-prod.fluidtopics.net/bFpGs_7qg1~lwFbw7~FTWQ "Test business logic and background processes by performing operations on the server."), the system executes the tests without displaying the Pick a Browser dialog.

## O que Fazer Depois

Monitor the progress of the tests. When complete, click Go to results on the progress dialog window to display the Test Results list, where you can [view](https://servicenow-prod.fluidtopics.net/jkbnoNHUgyQBnrNlhzG2lw "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.") and analyze the results.