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


---

# Automation framework

# Service Test Management automation framework {#ariaid-title1}

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

Service Test Management runs tests in the background with Workflow Studio flows and subflows. Events, a spoke selector, and templates start and extend them.
{#stm-automation-framework__table_ctp_y43_1lc__entry__2}

| Building block | Description |
|-|-|
| Flows and subflows | The application installs flows and subflows that start test group runs, run test runs, record results, evaluate them, and create tasks. For more information, see [Flows, subflows, and actions installed](https://www.servicenow.com/docs/2IPfvMKK6tDhJxvsmZEEDA "Find the flows, subflows, custom actions, events, and clean-up rules that Service Test Management installs to run tests in the background."). |
| Custom action types | Custom actions that the flows use, for example to prepare the request body, update the test run response, and calculate the result of a test run. For more information, see [Flows, subflows, and actions installed](https://www.servicenow.com/docs/2IPfvMKK6tDhJxvsmZEEDA "Find the flows, subflows, custom actions, events, and clean-up rules that Service Test Management installs to run tests in the background."). |
| Event and script action | The event `sn_st_mgmt.schedule_test_group_run` and its script action start a scheduled test group run at the right time. The application has no scheduled jobs for this. For more information, 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."). |
| Spoke selector | The Service Test Request in the spoke selector sends a test run to an external system through an adapter flow that you choose. For more information, 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."). |
| Extension point | The extension point `sn_st_mgmt.DiagnoseDataBrokerProcessor` lets another application supply the products and test definitions that apply to a task. The built-in implementation reads them from product inventory, configuration items, and the affected configuration items of the task. |
[Table 1. Building blocks]

{#stm-automation-framework__table_ctp_y43_1lc}

## Flow or subflow initiation {#stm-automation-framework__stm-automation-framework-triggers}

The following conditions initiate a flow or a subflow.

A test group run reaches the New state
:   The Execute Test Group flow starts and processes the draft test runs.

A scheduled time arrives
:   The event fires and the script action sets the test group run to New, which starts the flow above. The script action runs asynchronously.

An automated test group runs
:   The flow that you selected in the Flow field of the test group runs. That flow can call the Automated test run creation tool subflow once for each test definition.

A test run is executed
:   The Execute test run flow sends the test run through the spoke selector, and the flows that follow record and evaluate the result.

Repair tasks are needed
:   The application runs the Trigger resolution tasks for test groups subflow in the foreground and waits for it to finish.

## Customization options {#stm-automation-framework__stm-automation-framework-extend}

* To run tests against your own external system, copy the subflow TEMPLATE: Execute test run and register the copy as the adapter in the spoke selector. The subflow STM test run demo adapter shows a working adapter that simulates a result without an external system.
* To change how a test group is run, copy the subflow TEMPLATE: Execute test group and select the copy in the Flow field of an automated test group. A demo subflow with demo data is provided as a reference.
* To create test characteristics for each automated test run, select your own flow in the Test characteristics creation flow input of the Automated test run creation tool subflow.
* To decide which products and test definitions apply to a task, add your own implementation of the extension point.

{#stm-automation-framework__ul_ynx_lrf_blc}

Test runs that automation creates and evaluates are cleaned up after 30 days. 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.").
**Related concepts**   

* [Test run in Service Test Management](https://www.servicenow.com/docs/mQyxtyZ6LSDFrjdjg4fJ9Q "A test run is one execution of a published test definition that validates service behavior. Create test runs from a workspace, through the subflow, or from an external system using the TMF 653 API.")  
**Related tasks**   

* [Create a test group](https://www.servicenow.com/docs/E9yCzwdx3NcF8SguFSWkCg "Create a test group to group related service tests, such as speed and ping tests, to streamline diagnostics for specific service types or product models in Service Test Management.")

