Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

About the Tests Page

To access this page, click Observability > Active Assurance > Tests.

Tests are entities that you configure to measure metrics in a time-bound manner to produce a static measurement for the given duration. You (superusers and network administrators) can use the Tests page to view a list of Tests that the Test Agents run in your network and the details of these Tests. For more information, see Tests and Monitors Overview.

The widgets display the following information:

  • Total—The total number of Tests that you have run in your network.

  • Passed—The number of Tests completed successfully. Routing Director considers a Test as passed when the KPIs have not exceeded the evaluation criteria you have specified. Routing Director also displays the pass percentage of Tests.

  • Failed—The number of Tests that failed. Routing Director considers a Test as failed when any one of the KPIs have exceeded the evaluation criteria you have specified. Routing Director also displays the fail percentage of Tests.

  • Error—The number of Tests that have encountered errors. Routing Director also displays the error percentage of Tests. An error occurred can be of any reasons from a Test Agent being offline to a metric configuration failure or a timeout.

    Note:

    By default, these widgets display the data for the past 1 week. However, you can customize the data visualization for a specific time range. For example, if you click 2h, the widgets displays the Tests that were run for the past 2 hours.

You can view the following tabs on the Tests page:

  • Executions Tab—Displays all completed and in-progress executions. Use this tab to create a Test, view Test execution details such as status, timing, the user who triggered the Test, and so on.
  • Schedules Tab—Displays all schedules created for execution. Use this tab to view and manage schedules. You can add, pause, resume, and delete a schedule.

Tasks You Can Perform

You can perform the following tasks on the Executions tab:

  • View details of a Test—You can view the list of all the Tests that you have run and the details of Tests. To view the details of a Test, select a Test and click More > Details. You can also hover over the Test-Name and click the Detailed View icon. The Test execution details pane appears on the right side of the page displaying the Test details.

    On the Test execution details pane, you can:

    • Copy API Request URL—You can copy the API Request URL so that you can reuse the copied API request URL to fetch the Test details when you rerun the Test.

    • Download Results— You can download the Test result summary as a JSON file to your local system. When you click the Download results button, a JSON file is generated that you can download to your local system.

      The JSON file includes information displayed in the Tests execution details pane that can be used to analyze the results locally.

    • You can view additional information such as, Test ID, Test name, Test status (passed or failed), and so on.

    Click the Close (x) icon to close the pane.

  • View details of a selected Test. See About the Test-Name Page.

  • Create a Test. See Create a Test.

  • You can also perform the following tasks on this page:

    • Sort, resize, or re-arrange columns in a table (grid).

    • Show or hide columns in the table or reset page preferences, using the vertical ellipsis menu.

    • Filter the data displayed in the table—Click the filter icon (funnel) and select whether you want to show or hide advanced filters. You can then add or remove filter criteria, save criteria as a filter, apply or clear filters, and so on. The filtered results are displayed on the same page.

    For more information, see GUI Overview.

You can perform the following tasks on the Schedules tab:

  • View details of a schedule—You can view the list of all schedules and their details. Click a Schedule-Name to view the schedule details in edit mode. You can also click a Recurrence-Name to view the schedules in Calendar Preview.
    Note:

    To re-run a completed schedule, open the completed schedule in edit mode by clicking the Schedule-Name. You can modify the settings and click Save. When you save, the updated schedule reactivates and run again based on the new settings.

  • Add a schedule—You can create a schedule to run a Test automatically at defined intervals. Click Add Test Schedule to create a new schedule. For more information, see About the Measurement Designer Page.
  • Pause or resume a schedule—You can pause an active schedule to temporarily stop from triggering Test executions, and you can resume a paused schedule to restart Test executions. To pause or resume a schedule, select a schedule and click More > Pause Schedule or More > Resume Schedule.
  • Delete a schedule—You can delete a schedule that is no longer needed. To delete a schedule, select a schedule and click More > Delete. Once you confirm deletion, the schedule is deleted from the Schedules Tab.
  • You can also perform the following tasks on this page:

    • Sort, resize, or re-arrange columns in a table (grid).

    • Show or hide columns in the table or reset page preferences, using the vertical ellipsis menu.

    • Filter the data displayed in the table—Use filters to narrow down the Tests displayed in the table. Two filter modes are available:

      • Basic—Select one or more predefined filter criteria from the filter bar. You can filter by Test, Name, Tags, and Status, or use the More filters to perform a keyword search. To remove all applied filters, click Clear filters.
      • Raw—Specify a filter expression directly in the text field to query Tests using custom filter logic. For example, (test_agent.id='abc' OR test_agent.id='def') AND metadata.name='hello'.

    For more information, see GUI Overview.

Table 1: Fields on the Executions tab
Fields Description
Name The name of the Test that you specified when you created the Test.
Status The status of the Test:
  • Scheduled—The Test is scheduled to run.

  • Waiting—The Test Agent is getting ready to run the Test.

  • Running—The Test is running.

  • Stopping—The Test is being stopped and preparing the results.

  • Error—The Test has encountered an error while being executed by the Test Agent. The errors can be anything from a Test Agent being offline to a metric configuration failure or a timeout.

  • Passed—The Test has passed successfully.

  • Failed—The Test has failed because values for some metrics exceed the threshold you configured.

  • Canceled—The Test has been canceled by you. Routing Director retains the data related to the canceled Test up to the point of cancellation.

Status Message

The status message generated by Routing Director after you run a Test.

Execution Start Time

The date and time when the Test was executed. The timestamp is displayed in the following format: Month DD, YYYY, HH:MM:SS AM/PM.

For example, Feb 5, 2024, 4:29:52 PM.

Execution End Time

The date and time when the Test ended. The timestamp is displayed in the following format: Month DD, YYYY, HH:MM:SS AM/PM.

For example, Feb 5, 2024, 4:29:52 PM.

Executed By

The username (e-mail address) of the user who has run the Test.

Cancelled By

The email address of the user that has cancelled the Test.

Test Tags

The tags you have configured for the Test in the key:value format.

By default, only two tags are displayed in the column. To view more than two tags, click + Number more.

A tag is a key-value pair in which the key signifies a category for which you configure a value. The value is an identifier for the category.

Examples of key-value pairs are device and device name (edgedevice:acx7000), site and site name (site:bangalore).

You can configure tags for a Test at the time of creating a Test.

Table 2: Fields on the Schedules tab
Fields Description

Name

The name of the schedule.

You can identify a schedule based on the color you selected during schedule creation. The colored dot helps you quickly distinguish one schedule from another.

Test

The name of the Test that this schedule triggers.

Status

The status of the schedule. The available statuses are:

  • Active

  • Paused

  • Completed

Recurrence

The configured recurrence pattern in a readable format.

Click a Recurrence-Value to preview the schedule on a calendar.

ID

The Universal Unique Identifier (UUID) of the schedule.

Description

The description specified for the schedule.

Tags

The tags associated with the schedule in the key:value format.

Examples of key-value pairs are device and device name (edgedevice:acx7000), site and site name (site:bangalore).

Created by ID

Displays the unique identifier of the user who created the schedule.

Updated by ID

Displays the unique identifier of the user who last updated the schedule.

Color

Displays the color assigned to the schedule for visual identification.

Time zone

The time zone used to evaluate the recurrence pattern and upcoming execution times in Continent/City format.

For example, Asia/Calcutta.

Executions

The total number of Test executions that the schedule has triggered so far.

Start Time

The time elapsed since the schedule started, relative to the current time.

For example, 7 days ago, a month ago.

Click a Start-Time to view the date and time when the schedule started triggering executions. The timestamp is displayed in the following format: Month DD, YYYY, HH:MM:SS AM/PM.

For example, Feb 28, 2026, 4:29:52 PM.

End Time

The time elapsed since the schedule ended or is configured to end, relative to the current time.

For example, 7 days ago, a month ago.

Click a End-Time to view the date and time when the schedule is set to stop triggering executions. The timestamp is displayed in the following format: Month DD, YYYY, HH:MM:SS AM/PM.

For example, Feb 28, 2026, 4:29:52 PM.

Next Execution

The time elapsed until the next scheduled execution, relative to the current time.

For example, in 2 days, in 19 hours, in 59 minutes.

Click a Next-Execution-value to view the date and time when the schedule is set to trigger the next execution. The timestamp is displayed in the following format: Month DD, YYYY, HH:MM:SS AM/PM.

Empty if the schedule is paused or completed.

Last Execution

The identifier of the most recently triggered execution for the schedule.

Updated

The time elapsed since the schedule was last modified, relative to the current time.

For example, 2 days ago, 19 hours ago, 59 minutes ago.

Click an Updated-value to view the date and time when the schedule was last modified. The timestamp is displayed in the following format: Month DD, YYYY, HH:MM:SS AM/PM.

For example, Feb 28, 2026, 4:29:52 PM.

Created By

The e-mail address of the user who created the schedule.

Updated By

The e-mail address of the user who created the schedule.