> 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-plans/creating-a-test-plan/viewing-a-test-plan.md).

# Viewing a test plan

## 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="/files/6rM3UA0cwzsRf6g0mTkH" 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 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-plans/creating-a-test-plan/viewing-a-test-plan.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.