> 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-cases/overview.md).
# Overview
Learn what test cases are and how to access them in Test Context Manager.
## 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.
From this list, you can:
* sort records
* filter records
* search records
* group records
* choose visible columns
---
# 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-cases/overview.md?ask=&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.
