---
sourceDocument: Yokohama Build or modify applications
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/application-development

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Active scheduled test runners

# Active scheduled test runners {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

View the client test runners table filtered to show only those runners available to run
tests to be started by a schedule.
When you start a [scheduled
client test runner,](https://servicenow-prod.fluidtopics.net/Gb13MZuw~5KcqKEufdeI4g#atf-sched-suites "You can schedule a test suite to run at a specified date and time.") the system registers that runner in the Active Scheduled Test
Runners table.

The Active Scheduled Test Runner module is useful when you create a scheduled suite run.
For scheduled suite runs, you can specify the browser to use. To determine the name and
version of a browser you want to use, start a scheduled test runner with that browser, then
inspect that runner's record in the Active Scheduled Test Runners module.

The data in this table is transient. While the runner is active, it reports in to the system at a specified interval. If the runner does not report in at the expected time, the system marks the runner as inactive. After a period of time the system deletes the runner.

You can [modify these intervals](https://servicenow-prod.fluidtopics.net/co7M47uwZNuR_C8UXIwgZw "Modify how often active client test runners report in to the system and how long the system retains records for inactive client test runners.") on the [Automated Test
Framework properties](https://servicenow-prod.fluidtopics.net/kcx6hsY5387sFbfeJbFwlw "On the Properties form, you can set parameters that control how the system executes automated tests and test suites.") page.
Figure 1. Example Scheduled Client Runner Test table {#atf-active-sched-runners-module__table_vtz_r4g_sz__entry__2}

| Field / UI Element | Description |
|-|-|
| Type | Whether this test runner is for manual or scheduled tests. In the Active Scheduled Test Runners module, Type is always Scheduled. |
| User | The user logged into the browser session. |
| Browser name | The browser name. |
| Browser version | The browser version. |
| OS name | The name of the operating system running the browser. |
| OS version | The version of the operating system running the browser. |
| Status | Whether this runner is currently online or offline. In the Active Manual Test Runners module, Status is always Online. |
| Last checkin | The time/date this runner most recently reported in to the system. |
| Status reason | If the Status is Offline, the reason why. In the Active Scheduled Test Runners module, Status reason is always empty. |
[Table 1. Fields on the Client Runner Test table]

{#atf-active-sched-runners-module__table_vtz_r4g_sz}