Test Run

A Test Run is a group of executed probes performed at a specific point in time against your target. In each test run, you can choose which vulnerabilities to test by selecting one or more pre-configured probes.

To view the test run results and perform actions on an already triggered Test Run, go to the Test Run View page.

Starting a Test Run

The prerequisites for starting a new test run are as follows:

  • Existing Target, and

  • Configured Probes.

Check the Getting started guide.

To initiate a new test run, click the "New Test Run +" button on the Overview or Test Run page.

A dialog box will appear, prompting you to:

  • Enter the name of your run.

  • Select one or multiple probes to be included in the run.

  • Additionally, you can enable E-mail Notification or Schedule the Test Run for later.

Your available probe credits are displayed in the header. Each selected probe deducts from your total.

Figure 1: Start New Test Run

While the test run name can be duplicated, it will be treated as a new test run.

Test Run Notifications

To receive email notifications for a specific test run, enable the "Receive notifications" checkbox in the new test run modal.

Once the test run is complete, the user who initiated it will receive an email containing the test run details and the generated PDF report as an attachment.

For more information about the report, refer to the Test Run Report page.

Test Run Scheduler

The Test Run Scheduler enables you to plan and automate test runs at predefined times and frequencies, helping your team streamline evaluation workflows and reduce operational overhead. Instead of manually setting up tests every time you want to validate model behavior, scheduler allows you to set up recurring or single-run executions that run in the background.

Scheduler supports a wide range of use cases, from scheduled daily Context Leakage probe in production to monthly full security assessments—enabling consistent, repeatable testing practices aligned with your organization's policies and release cycles.

The Scheduled tab on the Test Runs page helps you manage upcoming test runs, giving you clear visibility into all scheduled executions.

Figure 2: Test Runs page - Scheduler tab

Creating Scheduled Test Run

Starting a new test run includes the option to schedule it for later .

Schedule a test run:

  1. Go to the Test Runs or Overview page.

  2. Click New Test Run.

  3. Configure the test name and select probes.

  4. Click Schedule for Later.

  5. Choose a date, time, and frequency for execution.

  6. Confirm with Schedule Test Run.

Optionally, you can choose to receive a Test Run Notification by checking the "Receive notification" checkbox

Figure 3: Creating new Scheduled Test Run

Managing Scheduled Test Runs

All scheduled test runs can be fully managed from the Scheduled tab on the Test Runs page. This page provides a centralized view of upcoming and recurring test runs, allowing you to take direct actions as needed.

Each scheduled test run includes three control icons:

  • Start Test Run – Manually trigger the test run immediately.

  • Edit Test Run – Modify the scheduled test run configuration.

  • Delete Test Run – Permanently remove the scheduled run.

If a test run is not currently needed, you can toggle its status to Inactive without deleting it. This is useful for temporarily pausing automated runs without losing their configuration.

Editing a Scheduled Test Run

Click the Edit Test Run icon to modify any existing scheduled run. The following parameters can be updated:

  • Test Run Name

  • Date and Time of Next Run

  • Frequency (e.g. Daily, Weekly, Monthly, Single Run)

  • Selected Probes (custom or predefined probes)

Once changes are made, click Save Changes to update the schedule.

Figure 4: Edit Scheduled Test Run

Last updated