> 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/overview.md).

# Overview

## Overview

Test cases are the core unit in Test Context Manager.

### What this feature does

A test case defines a scenario to verify.

It includes preconditions, steps, and expected results.

### What's included

This area lets you create, organize, search, and maintain test cases in the active project.

It also gives each test case a readable ID and a structured execution format.

### What's not included

Test cases do not group execution into releases or cycles.

Use test plans for execution setup and test runs for actual execution.

### How to access it

To open test cases:

1. Go to the sidebar.
2. Click **Test cases**.

The test case list shows all test cases in the active project.

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

From this list, you can:

* sort records
* filter records
* search records
* group records
* choose visible columns

<figure><img src="/files/IPLGdeGHDoXrJRlptgcw" 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-cases/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.