--- 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 --- # Getting started with the Automated Test Framework # Getting started with the Automated Test Framework {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 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 Getting started with the Automated Test Framework The Automated Test Framework (ATF) in ServiceNow enables customers to create, manage, and run automated tests for their instances. It supports a range of testing capabilities from basic form validations to complex server-side script testing. The framework helps ensure quality and reliability by automating repetitive testing tasks and validating functionality across various ServiceNow components. Show full answer Show less ## Key Features * **Test Step Configuration Categories:** ATF offers diverse test step types tailored for different components: * **Service Catalog in Service Portal:** End-to-end testing for catalog items, including variable settings, item quantity, price validation, ordering, and cart operations. * **Application Navigator:** Tests navigation features such as menu and module visibility and user navigation simulation. * **Custom UI:** Mimics user actions without scripting by setting component values, clicking components, and validating text and states. * **Form Testing:** Open forms, set and validate field values and states, interact with UI actions, and submit forms. * **Service Catalog:** Similar to portal testing but focused on catalog item operations within the platform. * **Forms in Service Portal:** Testing forms specifically within the Service Portal environment. * **REST:** Create and send inbound REST requests, test REST endpoints, and validate responses (status code, headers, time, and payload). * **Server:** Allows complex operations including JavaScript unit tests with Jasmine, testing business rules, script includes, and data-focused tests. * **Output Variables:** Many test steps return output variables that can be used as inputs for subsequent steps, enabling complex test flows such as testing record ownership changes or chained operations. * **Custom Test Step Configurations:** Customers can define their own server-side test steps with input and output variables to extend ATF testing capabilities beyond built-in steps. * **Data Preservation:** ATF automatically tracks and cleans up data created during tests, ensuring that test executions do not affect the instance state permanently. * **Test Suites:** Enables grouping multiple tests to run in order or hierarchically, with scheduling options to automate test execution times. * **Domain Separation Support:** ATF respects domain separation, allowing tests and data to be appropriately isolated based on domain configurations for secure and segmented testing. ## Practical Next Steps for ServiceNow Customers * Begin by following the tutorial to create and run a simple test, such as adding a new user record, to get familiar with ATF basics. * Explore test step categories relevant to your instance's key features (forms, Service Portal, Service Catalog, REST APIs, etc.) to build comprehensive tests. * Leverage output variables to create dynamic, multi-step test scenarios that reflect real-world workflows. * Consider creating custom server-side test steps if your testing needs extend beyond the built-in configurations. * Use test suites to organize and automate your tests, ensuring consistent quality checks through scheduled runs. * Ensure you understand domain separation implications to maintain proper data isolation in your testing processes. If you are new to the Automated Test Framework, read this overview to learn what the framework can do. Next, follow the tutorial to create and run a test that uses the most basic of ATF features. After you feel comfortable with the basics, explore more advanced features provided by the ATF.{#atf-intro__l5z_4y2_gy} ATF features provide flexibility in how you test your instance. ## Test step configuration categories {#atf-intro__section_oyy_5gl_kfb} {#atf-intro__table_bgz_wcg_kfb__entry__2} | Category | Description | |-|-| | Service Catalog in Service Portal | Perform end-to-end testing for a catalog item in the Service Portal. * Open a record producer, catalog item, or order guide. * Set variable values and catalog item quantity. * Validate variable values, states, price, and items included in an order guide. * Navigate in an order guide. * Open and toggle catalog items in an order guide. * Add an item or an order guide to a shopping cart. * Order a catalog item or an order guide. * Submit a record producer. {#atf-intro__ul_npn_k5l_kfb} | | Application Navigator | Create tests to check navigation features. * Verify that application menus are listed in the left navigation bar. * Verify that application modules are listed in the left navigation bar. * Navigate to a module as if a user clicked the module in the left navigation bar. {#atf-intro__ul_otg_3dg_kfb} | | Custom UI | Create simple tests that mimic user actions with no scripting. * Set component values. * Assert that specified text is or is not on a page. * Validate component values. * Click components. * Validate the states of components (read-only or not read-only). {#atf-intro__ul_cv4_2pl_kfb} | | Form | Create tests of forms. * Open a new form or an existing record. * Set field values. * Validate field values or field states (such as mandatory, not mandatory, read only, not read only, visible, and not visible). * Validate whether a UI action is visible. * Click a button on a modal page. * Click a UI action. * Submit a form. {#atf-intro__ul_u2x_hql_kfb} | | Service Catalog | Perform end-to-end testing for a catalog item. * Open a catalog item or a record producer. * Search for a catalog item. * Set variable values and catalog item quantity. * Validate variable values, states, and price. * Add an item to a shopping cart. * Order a catalog item. * Submit a record producer. {#atf-intro__ul_z41_jcd_zz} | | Forms in Service Portal | Create tests of forms in the Service Portal. * Open a form. * Set field values. * Validate field values or field states (such as mandatory, not mandatory, read only, not read only, visible, and not visible). * Validate whether a UI action is visible. * Click a UI action. * Submit a form. {#atf-intro__ul_nl2_vvl_kfb} | | REST | Create and send an Inbound REST request and verify the response. * Test any REST endpoint on the instance. * Use a REST request to create records, as well as retrieve, update, or delete records created in a previous test step or that already existed on the instance. * Verify the response status code, response headers, response time, and response payload. {#atf-intro__ul_dmx_4dg_kfb} | | Server | Perform more complex operations, including the following: * Perform unit tests using JavaScript, including tests using the Jasmine test framework. * Test business rules, script includes, and other scripts. * Create tests that operate on data that you define. {#atf-intro__ul_w5d_mdg_kfb} | [ ] {#atf-intro__table_bgz_wcg_kfb} ## Output variables Many test steps return output variables whose values you can use as inputs to a later step. For example, you can use output variables to accomplish the following tasks: * Perform a server-side assert on a record that you previously inserted. * Create a record as one user, and then reopen its form as a different user. {#atf-intro__hsg_3np_vw} ## Custom test step configurations {#atf-intro__section_wkg_lbl_kfb} In addition to the steps built into the Automated Test Framework, you can create custom test step configurations. These custom steps can take input variables and return output variables that you define. Note: You can only define custom test steps that run on the server. The Automated Test Framework does not support creating custom step configurations that run on the browser. ## Data preservation {#atf-intro__section_jd5_sbl_kfb} The Automated Test Framework automatically tracks and deletes any data created by running tests, and automatically rolls back changes after testing. ## Test suites {#atf-intro__section_c2m_wbl_kfb} Test suites enable you to execute a batch of tests in a specified order. In addition, test suites can be hierarchical, with suites nested within other suites. You can associate test suites with schedules that determine when the system runs the test suites. * **[Build and run your first automated test](https://www.servicenow.com/docs/v9HhH70YmAOYqpCfM0Npig#atf-tut-build-first)** Follow these step-by-step instructions to create and run your first automated test. This test creates a new user record. * **[Next steps with the Automated Test Framework](https://www.servicenow.com/docs/oLT7zBZVebsW3IjW6Yp3Qw)** After you feel comfortable creating and running simple tests, explore the more advanced features of the Automated Test Framework. * **[Domain separation and Automated Test Framework](https://www.servicenow.com/docs/O0rrZgFDLjkYcmKcvxMe1w)** Domain separation is supported in the Automated Test Framework. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.