> 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-cases/creating-a-test-case/viewing-and-editing-a-test-case.md).

# Viewing and editing a test case

## Viewing and editing a test case

Click any row in the test case list to open the detail page.

The detail page includes three tabs.

<figure><img src="/files/i5uPUaNfc7ozQg8faoaO" alt=""><figcaption></figcaption></figure>

| Tab      | What it shows                                                                                                       |
| -------- | ------------------------------------------------------------------------------------------------------------------- |
| Details  | All test case fields. You can edit fields inline. The test steps table also supports inline editing.                |
| Comments | Threaded discussion for the test case. Add a comment and click **Post**. Replies appear under the original comment. |
| History  | A log of each change, including who made it, when it changed, and the old and new values. This tab is read-only.    |


---

# 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-cases/creating-a-test-case/viewing-and-editing-a-test-case.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.