> For the complete documentation index, see [llms.txt](https://mozarkdocs.gitbook.io/appx_documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mozarkdocs.gitbook.io/appx_documentation/test-context-manager-documentation/test-runs/overview.md).

# Overview

## Overview

A test run is the execution of a test plan or a selected set of test cases.

### What this feature does

Use a test run to record real execution results for each test case and step.

### What's included

During a run, you execute each test case step by step.

For each step, you record whether it:

* passed
* failed
* was blocked
* was skipped

Test runs also capture evidence, comments, and linked defects.

### What's not included

A test run does not define the long-term structure of your repository.

Use test cases for reusable coverage and test plans for repeatable execution setup.

### Why it matters

Each run creates an execution record that feeds reports and test case history.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://mozarkdocs.gitbook.io/appx_documentation/test-context-manager-documentation/test-runs/overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.