--- sourceDocument: Brazil Build or modify applications sourceDocumentLink: https://www.servicenow.com/docs/r/application-development Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil Build or modify applications ft:clusterId : - cadev bundleId : - cadev workflow : - Development, Data, and Analytics --- # Building and running automated test suites # Building and running automated test suites {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Building and running automated test suites Automated test suites in ServiceNow allow you to group and run multiple tests in a specific order to validate an application or related features efficiently. A test suite can include individual tests and other test suites, supporting multi-level hierarchies for complex test organization. This structure enables streamlined execution, scheduling, and result tracking of tests. Show full answer Show less ## Key Features * **Hierarchical Test Suites:** Create parent and child test suites to organize tests logically, where a suite can contain both tests and other suites. * **Scheduling:** Schedule test suites to run automatically using schedule records linked to test suites, enabling automated and timed test execution. Note that only test suites (not individual tests) can be scheduled, and scheduled runs require an active client test runner with browser conditions met. * **Filters for Dynamic Test Addition:** Use filters to automatically add tests to a test suite based on criteria, reducing manual effort in maintaining test suites. * **Copy and Modify Test Suites:** Quickly create new test suites by copying existing ones, including their nested tests and child suites, and then rename or modify as needed. * **Run and Re-run Tests:** Execute test suites in non-production environments, run scheduled suites via scripts for immediate execution, and selectively re-run only failed tests within a suite to optimize testing cycles. * **Notifications:** Use watchlists on test suite run records to notify users via email upon completion of test suite execution. ## Practical Considerations for ServiceNow Customers * Ensure the client test runner is active and the browser is open and unlocked on the scheduled machine for UI-related test steps to run successfully. * Scheduling is flexible, allowing many-to-many relationships between schedules and test suites, enabling efficient test management. * Dynamic filters help automate test suite maintenance, saving time for test designers. * Running and scheduling test suites in non-production instances helps safely validate changes before deployment. * Use scripting capabilities to trigger test suites on demand, integrating tests into automated CI/CD pipelines or custom workflows. Run a group of tests in a specific order to test an application or a group of related features. A test suite can contain both individual tests and other test suites. A test suite that contains another test suite is called a parent, and the test suite contained within the parent is called a child. While a test suite can have both individual tests and test suites as children, tests cannot have other tests as children. Tests can only contain test steps. ## Benefits {#atf-suites-overview__section_czv_r23_5fb} Grouping tests into test suites offers these benefits. * Allows testers to run every test in a test suite with one action. * Allows testers to run all child test suites in a parent test suite. * Allows testers to see test results for every test in a test suite. * Allows test designers and testers to schedule when to run test suites. * Allows test designers and testers to schedule starting client test runners to support test runs. {#atf-suites-overview__ul_vc2_wwh_5fb} ## Hierarchies {#atf-suites-overview__section_fdw_5b3_5fb} Automated Test Framework supports building a multi-level hierarchies where a test suite can be both a parent and child. For example, this figure illustrates Test Suite 1 as the parent at the top of the hierarchy. Test Suite 1.3 is a child of Test Suite 1 and also a parent of Test Suite 1.3.1 and Test Suite 1.3.2. Figure 1. Example of Test Suite Hierarchy ## Schedules {#atf-suites-overview__section_lgc_gf3_5fb} To schedule a test suite, you need three components: * a test suite record * a schedule record specifying when you want the system to run the test suite * a scheduled suite run record that associates the test suite to run with the schedule for running it {#atf-suites-overview__pbf_3bt_bz} With this model, you can associate a schedule with many different test suites, and vice versa. Note: You can schedule only test suites, not individual tests. Scheduled tests will run only if there is an open Scheduled Client Test Runner page matching the scheduled suite's browser conditions. Scheduled tests cannot run on a machine that is locked, powered down, or does not already have the browser open. The watchlist on the test suite run record also allows you to specify users to receive an email when the system finishes executing the test suite run. If the test suite contains one or more form steps (steps involving a user interface), you must ensure that a scheduled client test runner is actively running in a browser when the schedule triggers the suite run. Note: See [Browser recommendations and requirements](https://www.servicenow.com/docs/KcCOTTLBP2efFp3gqPURyw#atf-test-runners__kvv_h25_gx) for recommendations and requirements for running the client test runner. For step-by-step instructions on how to schedule a test suite, see [Schedule an automated test suite](https://www.servicenow.com/docs/u_JKDgoPNpbJoIo~W~UpYg "Schedule one or more test suites to run at a specific date and time."). ## Filters {#atf-suites-overview__section_hjv_3f3_5fb} Automate the creation of test suites by using a filter to dynamically add tests to a test suite when they match the filter conditions. Reduce the time that your test designers spend manually creating and maintaining test suites. * **[Create an automated test suite](https://www.servicenow.com/docs/_l~zR8UDaqEAGOw8zS7fjw)** Group automated tests into a suite you can execute as a batch. * **[Copy an automated test suite](https://www.servicenow.com/docs/FFGdBjinFG2Nroxrmekt6A)** Reduce time when creating tests by copying an entire test suite. Rename and modify the test suite after copying. The Copy Test Suite button on the Test Suite form copies all the nested tests and child test suites within the text suite. * **[Add tests to a suite with a filter](https://www.servicenow.com/docs/pxQqqDyUWe5AsL_1A7bK6A)** Automate the creation of test suites by using a filter to dynamically add tests to a test suite when they match the filter conditions. Reduce the time that your test designers spend manually creating and maintaining test suites. * **[Add test to an existing automated test suite](https://www.servicenow.com/docs/~IrYyaBix8OvN44QKDkwfA)** Add a test to a test suite that already exists. * **[Add child test suite to parent test suite](https://www.servicenow.com/docs/KgqPI7Rq8Mc_gTWRIagh~A)** Add to a multi-level test suite by including a child test suite within a parent test suite. * **[Run an automated test suite](https://www.servicenow.com/docs/QcGk7XjccsyidmIXObxvQA)** After creating an automated test suite, run it in a non-production instance. * **[Schedule an automated test suite](https://www.servicenow.com/docs/u_JKDgoPNpbJoIo~W~UpYg)** Schedule one or more test suites to run at a specific date and time. * **[Run a scheduled test suite using a script](https://www.servicenow.com/docs/WE~0tI9KpZWVgsULO_mhIQ)** Execute a scheduled UI test suite immediately using a script without having to wait for the scheduled time. You can use this method while trying to automate the process of running a test. * **[Re-run failed tests in an automated test suite](https://www.servicenow.com/docs/9aLaP2rEBW8azNmiOaWh6w)** Re-run failed tests within a test suite without rerunning the entire suite. **Related concepts** * [Building and running automated tests with the Automated Test Framework](https://www.servicenow.com/docs/~rGzUuUe6SvRcy54K3G5IQ "Basic tasks in the Automated Test Framework.") * [Cancelling automated tests and test suites](https://www.servicenow.com/docs/bTlHJCJJ3bLKdlw8WbSr8Q#atf-cancelling "You can cancel automated tests and automated test suites that are running or are queued to run.") * [Suites](https://www.servicenow.com/docs/qWi9TCl_3gZG_DGP7ngHoA "The Suites module opens the Test Suites table. You can create, edit, and run test suites from this table.") **Related tasks** * [Auto-generate ATF tests](https://www.servicenow.com/docs/nfxBh4UzG6bNpz4pzFfhyA "Auto-generate ATF tests by selecting the auto-generate option either from the Auto-generate Tests module or Tests/Suites modules.") **Related reference** * [Step results record](https://www.servicenow.com/docs/MYXnXB82fGT1XOtVGDxefw "The Step Results record contains information about one step in a test result. You access specific step results from the Step Results related list in the Test Results record.")