---
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


---

# Test run execution

# Test run execution {#ariaid-title1}

Release version: Brazil  
Updated October 13, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
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.

## Test execution against external systems {#test-run-execution__test-run-execution-steps}

For a test that runs against an external system, the system works through these steps:

1. The Execute test run flow takes one test run.
2. The flow builds a request body from the test run and its test measure definitions, and sends a Service Test Request through the spoke selector. See [Service Test Request spoke selector](https://www.servicenow.com/docs/prFCbIk6svDMmt~WoocJ_w "Review the request type, its inputs and output, and the request definition that selects the adapter flow that runs a test against an external system.").
3. The adapter flow that the spoke selector selects sends the request to the external system and receives the response.
4. The system writes the response to the test run, and writes the returned values to the test measures.
5. The system calculates the result of the test run and compares each value with the threshold rules.
6. If a value breaks a threshold rule, the system creates a threshold rule violation and applies the measure consequences. For a failed test run that is linked to a service problem case, the system can also create resolution tasks.

{#test-run-execution__ol_txb_4kf_blc}

The result is one of Pass, Fail, Inconclusive, or Timed out. The result is separate from the state of the test run. See [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.").

## Reporting test results from an external system {#test-run-execution__test-run-execution-external}

An external system can run the test itself and report back instead of using the spoke selector. It updates the test run through the Service Test Management Open API (TMF 653). The update can set the state, the start and end times, the
validity period, the characteristics, and the test measures, including their violations and applied consequences. See [Recording test results and violations](https://www.servicenow.com/docs/CQSefN740gcuf96~EMA2_Q "Test measures, threshold rule violations, and applied consequences are sent by external systems and stored against a parent record. When a duplicate is received, the system updates the existing record rather than creating a new one.").

## Test run retention period {#test-run-execution__test-run-execution-retention}

A scheduled clean-up deletes test runs in the Cancelled, Completed, or Failed state 30 days after they were created, together with the records that depend on
them.
**Related concepts**   

* [Test group run and test run states](https://www.servicenow.com/docs/1XuFun8e4f1uGJI4Qt_u1g "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.")  
**Related tasks**   

* [Review a test run](https://www.servicenow.com/docs/MJPRalioGvjbYCj9L5ITAw "Check the state and result of a test run, the test definition and test group run that it belongs to, and the test measures that it captured.")