# Probe Run

Each Test Run consists of one or more **Probes** that create test cases and perform testing on your application. All test cases within a single probe run are **associated with the specific vulnerability** that the probe is designed to detect.

{% hint style="info" %}
To start your **first Probe Run**, you need to [start a Test Run](/ai-red-teaming/probe/test-run.md#starting-a-test-run).
{% endhint %}

The probe implements **various strategies and techniques** to identify its target vulnerability within your conversational application. Despite these variations, all test cases share the specific domain of your chatbot and the details that you defined in the probe's optimization.&#x20;

{% hint style="info" %}

* Go to the [**Probe Run View**](/ai-red-teaming/probe/probe-run/probe-run-view.md) to see detailed results for a **specific** Probe Run.
* Go to the [**Probe Overview**](/ai-red-teaming/probe/overview-page.md) to see all **latest probe runs**, regardless of the Test Run they belong to.
  {% endhint %}

<figure><img src="/files/8DZMY5y8hhRbx44QHlOM" alt=""><figcaption><p>Figure 1: Overview Page With Cards for Security Category Probes </p></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.probe.splx.ai/ai-red-teaming/probe/probe-run.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
