> 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.md).
# Creating a test plan
## Creating a test plan
### Before you start
Make sure the test cases you want to include already exist.
Decide the plan name, environment, and any execution configuration you want to track.
To create a test plan:
1. Open **Test Plans** from the top sub-navigation or sidebar.
2. Click **Create Test Plan**.
3. Enter a name.
4. Fill in any other fields you need.
5. In **Linked Test Cases**, click **Add Test Cases**.
6. Search for test cases by name or ID.
7. Select the test cases to include.
8. Click **Save**.
The plan name is required.
{% hint style="info" %}
Some workspaces let you create a test plan with AI.
{% endhint %}
### Expected result
The new plan is saved with its linked test cases and execution setup.
You can open the plan later and create test runs from it.
### Next step
When the plan is ready, continue with [Creating a test run](/appx_documentation/test-context-manager-documentation/test-runs/creating-a-test-run.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 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.md?ask=&goal=
```
`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.