> 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/creating-a-test-case.md).
# Creating a test case
Create a test case and add test steps.
## Creating a test case
### Before you start
Make sure you are in the correct project.
Decide the scenario, test data, and expected result before you begin.
To create a test case:
1. Open the **Test Cases** page.
2. Click **Create** in the top right.
3. Enter a title.
4. Fill in any other fields you need.
5. Click **Add Step** to add a step.
6. Enter **Action**, **Test Data**, and **Expected Result** for each step.
7. Drag rows to reorder steps if needed.
8. Click **Save**.
The title is the only required field for the initial save.
After saving, Test Context Manager assigns a readable ID automatically.
Examples include `TC-001` and `TC-002`.
### Expected result
The new test case is saved in the active project with its own ID.
You can open it again, edit its details, and add it to a test plan.
### Next step
To review or refine the saved record, see [Viewing and editing a test case](/test-context-manager-documentation/test-cases/creating-a-test-case/viewing-and-editing-a-test-case.md).
For bulk creation, use CSV import. See [Importing test cases from CSV](/test-context-manager-documentation/test-cases/creating-a-test-case/importing-test-cases-from-csv.md).
---
# 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/creating-a-test-case.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.
