> For the complete documentation index, see [llms.txt](https://docs.mozark.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mozark.ai/test-context-manager-documentation/test-plans/creating-a-test-plan/viewing-a-test-plan.md).

# Viewing a test plan

Open a test plan and review progress, linked cases, runs, and history.

## Viewing a test plan

Open any row in the test plan list to view its details.

The detail page includes these sections and tabs.

### Execution scoreboard

This summary shows execution progress across linked test cases.

It includes counts for:

* `Passed`
* `Failed`
* `Blocked`
* `In Progress`
* `Not Started`

### Linked test cases

This table lists all linked test cases.

For each test case, you can review:

* latest execution status
* last executed date

### Test runs

This section lists test runs created from the plan.

### Tabs

| Tab      | What it shows                     |
| -------- | --------------------------------- |
| Details  | All editable fields for the plan. |
| Comments | Discussion thread for the plan.   |
| History  | Full change history for the plan. |

<figure><img src="https://95054152-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIgQEgtjvk4zIWyVkgQ5o%2Fuploads%2Fijwp5CbVYe8am1bpfYkV%2FScreenshot%202026-07-01%20at%202.30.58%E2%80%AFPM.png?alt=media&amp;token=6300bc18-195c-496e-98b8-1cb850e3259e" alt=""><figcaption></figcaption></figure>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mozark.ai/test-context-manager-documentation/test-plans/creating-a-test-plan/viewing-a-test-plan.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.