Test Run View

Test Run View page displays details for a triggered Test Run. At the top of the page, you will find the total number of test cases and the number of failed and error test cases from all included probes. The execution date and time are displayed next to the status and progress bar. The test run's progress indicates the percentage of completed attacks out of the total scheduled. A Sankey diagram, and the probes table, visualize and display an overview of the results for each probe.

This page can be accessed by selecting the Test Run from either the Overview or Test Run History page.

To start a New Test Run, check Starting a New Test Run.

From this page, you can perform the following actions:

Test Run Statuses and Progress

Every Test Tun can have one of the following statuses:

  • Pending: The test run will start when the queue is clear.

  • Running: The test run is in progress.

  • Finished: All scheduled probes and their attacks are completed.

  • Canceled: The test run was canceled by the user before completion.

  • Error: The test run was aborted due to target misconfiguration.

Figure 1: Test Run View for test run named "Demo 2"

Test Run Results

The Test Run View page also displays and visualizes the data from all the Probes selected for a specific Test Run. It includes a Sankey Diagram, and the Probes Table, which provides an overview of the results for each Probe.

Sankey Diagram

A Sankey diagram visualizes the flow of data from one node to another, with the width of the flow representing the quantity or magnitude of the data. In this context the data represents executed test cases against your target.

The diagram illustrates the flow from the probe categories to specific probes visualizing the ratio of executed test cases between probes.

From the single probe, the flow connects towards passed, failed and error test case outcome, where the width of each flow indicates the number of test cases. Passed, failed and error nodes show total number of corresponding test cases in the test run.

The gradient from green to red visually represents the ratio of failed to passed test cases for each node. Nodes with fewer failed test cases appear greener, while those with more failed test cases appear redder. This provides a clear visual summary of the test run results.

Probes Table

In the Test Run View, the Probes Table lists all probes executed in that Test Run. The probes are grouped by category and display the total number of executed test cases (attacks), along with the counts of passed, failed and error test cases. A progress bar is also visible.

The terms "attack" and "test case" refer to the same concept and are used interchangeably throughout this documentation.

By clicking on the table row, you can navigate to the Probe Run details for the selected Probe within the Test Run.

To better understand how concepts like Test Run, Probe Run, and Test Case are linked from a broader perspective, see the Hierarchy of Concepts.

Canceling a Test Run

To stop a test run in progress, open the Test Run View and click the "Cancel Test" button. This will abort the test run and stop all probes. All attacks executed up to that point will remain visible and will be included in the results.

Re-Running a Test Run

You can re-run an existing test run by clicking the "Re-Run Test" button in the top right corner of the Test Run View. A test run cannot be rerun until it is either completed or stopped.

Deleting a Test Run

You can delete a test run by clicking the “Delete Test” button located in the top right corner of the Test Run View.

Last updated