> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-protection-protection/api-security-testing/ast-basics-and-workflow/scan-details/tests.md).

# Tests

Review the tests an API Security Testing scan ran, grouped by plugin category and endpoint, with their statuses and test chain results

***

<details>

<summary>Updates (October 2026 to December 2026)</summary>

* *October 2026* -
  * Updated the **Tests** tab to group executed tests by plugin execution category, with a status breakdown for each endpoint. Go to [Understand the Tests tab](#understand-the-tests-tab) for more details.
  * Updated the **Tests** tab to include information about test chain results for a test against an API endpoint. Go to [Test chain results](#test-chain-results) for more details.

</details>

The **Tests** tab provides information on all the tests Traceable executed during a scan run. A single scan can generate a very large number of tests, so Traceable groups them by plugin category and then by API endpoint, condensing the results into a few pages. This gives you an overview of how each category of attack performed across your endpoints, and lets you drill down to an individual test when you need to debug it.

## What you will learn from this topic

By the end of this topic, you will be able to understand:

* The way Traceable groups tests by plugin category, API endpoint, and test.
* The statuses displayed in the test status breakdown.
* The test chain results Traceable displays for a scan run.
* The way you can use test data to debug and improve endpoint testing.

***

## Before you begin

Make a note of the following before you review the tests in a scan:

* Ensure that the scan has completed at least one run, as Traceable lists tests per scan run. Go to [Scan Runs](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-protection-protection/api-security-testing/ast-basics-and-workflow/scan-details/scan-runs.md) for more details.
* Ensure that you are using CLI version *2.8.0* or above to view test chain results. With an earlier CLI version, Traceable displays only individual tests.
* Make sure that you understand mutations, because the test details display the mutations Traceable applied to each request. Go to [Mutation and Assertion Overrides](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-protection-protection/api-security-testing/advanced-usage/mutation-and-assertion-overrides.md) for more details.

***

## Understand the Tests tab

The **Tests** tab displays the tests that Traceable executed during a scan run, grouped by plugin category. A scan can generate a very large number of tests, so this grouping condenses the results into a few pages, which gives you a general overview of how each category of attack performed across your API endpoints. The tab displays data for one scan run at a time.

{% hint style="info" %}
Traceable selects the latest scan run by default. Use the scan drop-down at the top of the tab to view the tests for a different scan run.
{% endhint %}

<figure><img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-e3d417e52a5ca7a5869c5f4086a83e38f61400b9%2Ftraceable_ast_scandetails_tests.png?alt=media" alt=""><figcaption><p>Tests tab for a scan</p></figcaption></figure>

### Plugin execution categories

Plugin execution categories group plugins based on the type of security testing they perform. You can use this level to see which types of attacks Traceable ran during the scan run, and how many endpoints and tests each one covered. The top level lists each plugin execution category that Traceable tested during the scan run, such as *Access Control*, *NoSQL Injection*, and so on. Go to [Plugins](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-protection-protection/api-security-testing/advanced-usage/plugins.md) for more details on plugins. Each category row displays the name of the category and the following details:

| Field             | Description                                                                  |
| ----------------- | ---------------------------------------------------------------------------- |
| **API Endpoints** | Displays the number of API endpoints that Traceable tested for the category. |
| **Tests**         | Displays the number of tests that Traceable executed for the category.       |

{% hint style="info" %}
**Tests** field displays the number of tests executed, not generated.
{% endhint %}

### API endpoints

The API endpoint level shows how the tests in a category performed against each endpoint, which helps you identify the endpoints with the most vulnerable or failed tests without opening every test. When you expand an execution category, Traceable lists the API endpoints tested for it as **Endpoint**, along with the following details:

| Column                    | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Endpoint**              | Displays the method and path of the API endpoint.                                                                                                                                                                                                                                                                                                                                                                                                             |
| **Service**               | Displays the backend service or application that handles or exposes the API.                                                                                                                                                                                                                                                                                                                                                                                  |
| **Test Status Breakdown** | <p>Displays the number of tests executed against the endpoint for the category, split by the following statuses:</p><ul><li><em>Vulnerable</em>: The test detected an issue in the endpoint (shown in red).</li><li><em>Not Vulnerable</em>: The test did not detect any issue in the endpoint (shown in green).</li><li><em>Skipped</em>: Traceable did not execute the test (shown in yellow).</li><li><em>Error</em>: The test did not complete.</li></ul> |

### Tests

The test level lists the individual tests behind the status breakdown of an API endpoint, which helps you find the specific test you want to investigate. When you expand an endpoint, Traceable lists the tests executed against it for that category as **Test**. The following details about the test are shown:

| Column                 | Description                                                                                                                                     |
| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test**               | Displays the name of the test executed against the endpoint.                                                                                    |
| **Status**             | Displays the status of the test as *Vulnerable, Not Vulnerable, Skipped* or *Error.*                                                            |
| **Vulnerability**      | The vulnerability type for which the test was executed.                                                                                         |
| **Execution Category** | Displays how the execution of the test concluded, for example, *Success*. Go to [Execution categories](#execution-categories) for more details. |

Traceable displays the first five tests, followed by a **View more Tests** link with the count of remaining tests. Click a test to open its slide-out panel. Go to [Understand the test slide-out panel](#understand-the-test-slide-out-panel) for more details.

### Actions in the Tests tab

The actions in the **Tests** tab help you narrow a scan run's tests down to a specific category, status, execution outcome, or endpoint. Traceable provides the following actions in the tab:

| Action          | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
| --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Filter** icon | <p>Refines the data displayed in the tab by the following attributes:</p><ul><li><strong>Category</strong>: The plugin category of the test. This is the default filter.</li><li><strong>Status</strong>: The result of the test, such as <em>Vulnerable</em>, <em>Not Vulnerable</em>, or <em>Skipped</em>.</li><li><strong>Vulnerability Type</strong>: The vulnerability type for which Traceable executed the test.</li><li><strong>Execution Category</strong>: The execution outcome of the test, such as <em>Success</em>, <em>Target Connectivity Issue</em>, <em>Dependency Unmet</em>, or <em>Error Expected</em>.</li><li><strong>API Endpoint</strong>: The API endpoint against which Traceable executed the test.</li></ul><p>After you apply a filter, you can save it for later use under <strong>Filter → Saved</strong>.</p> |
| **Search** bar  | Locates a specific plugin category by typing its name.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |

***

## Understand the test slide-out panel

The test slide-out panel provides granular details about a test executed against an API endpoint. You can use it to see how Traceable built and sent the test, how the endpoint responded, and why the test reached its result. Click a test to open the panel. The top of the panel displays the plugin category, such as *Active*, followed by the test name. Go to [Configuring and Writing Custom Plugins](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-protection-protection/api-security-testing/advanced-usage/plugins/configuring-and-writing-custom-plugins.md#traceable-platform-recommended) for more details on plugins and its categories. The panel also displays the following details:

| Field                  | Description                                                                                                                                |
| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| **Endpoint**           | Displays the method and path of the API endpoint that Traceable tested.                                                                    |
| **Service**            | Displays the backend service or application that handles or exposes the API.                                                               |
| **Status Code**        | Displays the status code the endpoint returned for the test request.                                                                       |
| **Execution Category** | Displays the execution outcome of the test, for example, *Success*. Go to [Execution categories](#execution-categories) for more details.  |
| **URI**                | Displays the full URI[^1] of the test request. You can copy the URI using the **Copy** icon next to it.                                    |
| **Duration**           | Displays the time the endpoint took to respond to the test request.                                                                        |
| **Original Trace Id**  | Displays the ID of the trace on which Traceable based the test. You can copy the ID, or click the arrow icon next to it to open the trace. |

The panel also provides the following actions, located at the top:

* **View Traces**: Opens the traces associated with the test.
* **Copy as cURL**: Opens the **Copy cURL command for reverification** pop-up window. You can click **Copy** to copy the test request as a cURL command and run it yourself.

<figure><img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-29d5e055a8a763543614b22ae62ce9217c42dbaa%2Ftraceable_ast_scandetails_tests_slideout.png?alt=media" alt="Traceable APIST Scan Details Tests tab showing slide-out panel"><figcaption><p>Test details</p></figcaption></figure>

{% hint style="info" %}
Traceable does not capture traces for a test in the following scenarios:

* The test status is *Error* (the APIs are not reachable).
* The **Category** of the identified vulnerability is *TLS*.
* The **Attack Methodology Type** for a plugin is *Passive*.
  {% endhint %}

### Test chain results

Some plugins validate a potential vulnerability in stages instead of reporting it based on a single test. Traceable runs these stages as a *test chain*: a sequence of tests in which each test runs only when the result of the test before it meets the condition required to proceed. This staged approach improves confidence in a finding and reduces false positives caused by temporary network latency, server load, or random fluctuations in response time.

The chain consists of two stages. The initial stage establishes how the endpoint normally behaves and checks its response to an initial payload. These steps do not report vulnerabilities on their own. The validation stage uses a stronger payload to validate the behavior and repeats the test to confirm that the result is reproducible. Traceable reports a vulnerability only after the chain confirms it.

For example, a blind *SQL injection* test chain progresses through the following steps:

1. Traceable sends the original request without any mutation to confirm that the endpoint normally responds quickly.
2. Traceable injects a SQL time-delay payload and verifies that the response is delayed by the expected amount.
3. Traceable injects a longer time-delay payload and verifies that the response is delayed by a correspondingly longer amount.
4. Traceable repeats the longer time-delay payload to confirm that the behavior is reproducible, and reports a *Blind SQL Injection* vulnerability.

If any step's result does not meet the condition for the next step, Traceable does not execute the remaining steps and assigns them the *Dependency Unmet* execution category.

When a test belongs to a chain, the slide-out panel displays a **Test Chain** section above **Evidence**. The section lists the steps of the chain, for example, **Step 1** → **Step 2** → **Step 3**, and an icon marks the step of the test you opened. Click any step to view the evidence for that step.

<figure><img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-1e4332200fa819aebeeaf5df59d7646f5883a463%2Ftraceable_ast_scandetails_tests_testchainresults.png?alt=media" alt="Traceable APIST Scan Details Tests page Test chain results"><figcaption><p>Test chain results</p></figcaption></figure>

{% hint style="info" %}

* Test chain results are available only when you use Traceable CLI version *2.8.0* or above.
* With an earlier CLI version, the slide-out panel displays only individual tests.
  {% endhint %}

### Evidence

The **Evidence** section displays the request and response of the test across two tabs. You can use it to see exactly what Traceable sent to the endpoint, how it changed the original request, and how it decided whether the response was vulnerable.

{% tabs %}
{% tab title="Request" %}
The **Request Viewer** displays the request Traceable sent to the endpoint. You can toggle **Raw Body** to view the unformatted body, expand the viewer to full size, and use the find bar to search the body.\
The **Mutations** panel next to the viewer lists the modifications Traceable made to the original request, for example, changing a request parameter's value to a possible local file path. Go to [Mutation and Assertion Overrides](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-protection-protection/api-security-testing/advanced-usage/mutation-and-assertion-overrides.md) for more details.
{% endtab %}

{% tab title="Response" %}
Displays the response the endpoint returned for the test request. You can use this data to debug the endpoint and confirm whether sensitive data is being exposed through the API.\
The **Assertions** panel next to the viewer lists the validations that Traceable executed against the response to determine whether the test detected a vulnerability. For example, an assertion can require that the response returned by the API matches a local file response pattern, which indicates that the endpoint exposed a local file. You can expand an assertion to view its full details, and add new assertions or modify the existing ones according to your requirements. Go to [Mutation and Assertion Overrides](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-protection-protection/api-security-testing/advanced-usage/mutation-and-assertion-overrides.md) for more details.
{% endtab %}
{% endtabs %}

### Execution categories

The execution category tells you how the execution of a test concluded. Use it alongside the **Status** of a test, because a test that did not complete is not the same as a test that found no vulnerability. You can find execution categories in the API Endpoints dropdown and the test slide-out panel. Traceable assigns one of the following execution categories to each test:

| Execution category            | Description                                                                                                                                                                                            |
| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Success**                   | Indicates that Traceable executed the test and received a response from the endpoint.                                                                                                                  |
| **Error Expected**            | Indicates that the endpoint returned an error response that the test anticipated as part of its validation.                                                                                            |
| **Connection Timeout**        | Indicates that the endpoint did not respond to the test request within the allowed time.                                                                                                               |
| **Connection Reset**          | Indicates that the connection to the endpoint was closed while the test request was in progress.                                                                                                       |
| **Connection Refused**        | Indicates that the endpoint's host rejected the connection, for example, because no service was listening on the target port.                                                                          |
| **Network Error**             | Indicates that a network failure prevented the test request from reaching the endpoint.                                                                                                                |
| **Target Connectivity Issue** | Indicates that Traceable did not send the test because earlier requests to the same host had already failed to connect.                                                                                |
| **Dependency Unmet**          | Indicates that the test is part of a test chain, and the result of the preceding step did not meet the condition required to run it. Go to [Test chain results](#test-chain-results) for more details. |
| **Execution Error**           | Indicates that Traceable encountered an error while executing the test.                                                                                                                                |
| **Test Skipped**              | Indicates that Traceable did not execute the test during the scan run.                                                                                                                                 |
| **Policy Forbidden**          | Indicates that Traceable did not execute the test because the policy selected for the scan does not permit it.                                                                                         |
| **API Filter Mismatch**       | Indicates that Traceable did not execute the test because the endpoint does not match the API filters configured for the scan.                                                                         |
| **Unspecified**               | Indicates that Traceable did not record an execution category for the test.                                                                                                                            |

***

## Leverage the data shown in the tab

Consider that you ran a scan and navigated to the **Tests** tab to validate the executions. Instead of scrolling through every test, you expand the *Authorization* category and notice that the test status breakdown for the `POST /login` endpoint shows a high count of *Error* tests. You expand the endpoint, click one of the tests, and the slide-out panel shows that the connection timed out while the test was running. This indicates that the endpoint may have been unresponsive during the scan or may have a misconfiguration. You can click **Copy as cURL** to reproduce the request yourself, fix the endpoint's availability or configuration, and run the scan again.

You can use the data shown in the **Tests** tab to:

* Identify the plugin categories and endpoints with the most vulnerable or failed tests, without reviewing every test.
* Verify the detected issues (vulnerabilities).
* Analyze how Traceable executed a test, the mutations it applied, and the reason for any failure.
* Enhance the test logic by modifying the tests to meet your requirements.

***

## Demo

The following demo walks you through the test page and the details of tests run against API endpoints:

{% @arcade/embed url="<https://app.arcade.software/share/J2Ru7gpLcwyZOZ0H1M0M>" flowId="J2Ru7gpLcwyZOZ0H1M0M" %}

***

## Resume scan analysis

Once you have reviewed the executed tests, you can continue your analysis in the other tabs of the Scan Details page:

* To see the vulnerabilities these tests detected, open the **Issues** tab. Go to [Issues](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-protection-protection/discovery/risk/issues-overview.md) for more details.
* To see how many tests ran against each endpoint, open the **API Coverage** tab. Go to [API Coverage](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-protection-protection/api-security-testing/ast-basics-and-workflow/scan-details/api-coverage.md) for more details.
* To understand why no tests were generated for an endpoint, open the **Reachability Tests** tab. Go to [Reachability Tests](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-protection-protection/api-security-testing/ast-basics-and-workflow/scan-details/reachability-tests.md) for more details.
* To compare test counts across executions of this scan, open the **Scan Runs** tab. Go to [Scan Runs](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-protection-protection/api-security-testing/ast-basics-and-workflow/scan-details/scan-runs.md) for more details.

[^1]: Uniform Resource Identifier
