--- sourceDocument: Brazil Telecommunications, Media, and Technology sourceDocumentLink: https://www.servicenow.com/docs/r/telecom-media-technology Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil Telecommunications, Media, and Technology ft:clusterId : - telmt bundleId : - telmt workflow : - Customer and Industry --- # Run states # Test group run and test run states {#ariaid-title1} Release version: Brazil Updated October 13, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Test group runs and test runs move through system-controlled states. The state determines what the system does next, what an external system can update, and when records are deleted. The State field of a test group run and of a test run is read-only on the form. The system, a flow, or an external system changes it. ## Test group run states and transitions {#stm-run-state-model__stm-run-state-model-group-run} A test group run has seven states. The default state is Draft. {#stm-run-state-model__table_stm_group_run_states__entry__2} | State | Meaning | |-|-| | Draft | The test group run is created but not started. This is the default. | | Scheduled | The test group run is created with a scheduled time and is waiting for that time. | | New | The test group run is ready to run. Execution starts from this state. See [Test group run in Service Test Management](https://www.servicenow.com/docs/igrio9Ez_w1t5l0t2rztZA "A test group run captures one execution of a published test group and provides a structured record of test runs, measures, and characteristics."). | | Pending for input, In progress, Cancelled, Completed | The test group run is waiting for input, running, stopped before it finished, or finished. | [Table 1. Test group run states] {#stm-run-state-model__table_stm_group_run_states} {#stm-run-state-model__table_stm_group_run_transitions__entry__3} | From | To | What causes it | |-|-|-| | Draft | Scheduled | The test group run is created with a scheduled time. The business rule Add schedule run event to queue sets the state and queues a timed event. | | Draft | New | You start the run from a workspace without a scheduled time. The system sets the state immediatly. | | Scheduled | New | The scheduled time arrives. The script action Execute test group run on specific time sets the state, but only if the state is still Scheduled. The script action runs in the background. | | New | Other states | The flows that run the test group run set the next states. | [Table 2. Test group run transitions] {#stm-run-state-model__table_stm_group_run_transitions} ## Test run states {#stm-run-state-model__stm-run-state-model-test-run} A test run has ten states. The default state is New. The result of a test run is a separate field with the values Pass, Fail, Inconclusive, and Timed out. {#stm-run-state-model__table_stm_test_run_states__entry__2} | State | Meaning | |-|-| | Draft | The test run is prepared but not started. The workspace or the Automated test run creation tool subflow create test runs in this state. The Execute Test Group flow processes the draft test runs of a test group run. | | New | The default state of a test run that is created without one. | | Acknowledged | Test runs in this state appear in the Scheduled list under Test Runs in the application menu. | | Pending for Input, Rejected, Pending, In progress | The test run is waiting for input, was rejected, is waiting, or is running. | | Cancelled, Completed, Failed | The test run has ended. The system deletes test runs in these states 30 days after they were created. | [Table 3. Test run states] {#stm-run-state-model__table_stm_test_run_states} An external system can set the state of a test run when it updates the test run through the Service Test Management Open API (TMF 653). See [Test run execution](https://www.servicenow.com/docs/4PU4roaxPDkmlA2mhoMbGQ "When a test run is triggered, the system sends a request to the external system through a spoke, records the response, and calculates the result. An external system can also run the test and report back through the Service Test Management Open API."). ## State rules and constraints {#stm-run-state-model__stm-run-state-model-rules} * A test group run can reference only a published test group, and a test run can reference only a published test definition. * A scheduled test group run starts only if its state is still Scheduled when the scheduled time arrives. * The Execute Test Group flow processes only the draft test runs of a test group run. * The system deletes test runs in the Cancelled, Completed, or Failed state 30 days after they were created. * The system doesn't let you close a diagnostic task that is marked Automated. {#stm-run-state-model__ul_hdt_gnf_blc} **Related concepts** * [Service Test Management automation framework](https://www.servicenow.com/docs/2W5Dv_R8dQGXdbTyPEtq8Q "Service Test Management uses flows and subflows to run tests in the background. Events, a spoke selector, and templates start and extend them. You can add your own flows and extension points to customize the behavior.") **Related reference** * [States and choice values](https://www.servicenow.com/docs/LAJ7hQaQP~Umdy410AUHSw "Review the states and the choice list values that the Service Test Management records use.")