> 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/getting-started/overview/basic-navigation.md).

# Basic navigation

Find the main areas of Test Context Manager and move between core workflows.

Test Context Manager uses the left sidebar to organize your workflows and give you quick access to every major area.

#### Sidebar

Use the left sidebar to move between the main areas of the product. Common entry points include:

* Test Cases
* Test Plans
* Test Runs
* Requirements
* Bugs
* Reports

<figure><img src="https://95054152-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIgQEgtjvk4zIWyVkgQ5o%2Fuploads%2F5XSfDo9WpX9Far2BeQxR%2FScreenshot%202026-07-01%20at%201.37.10%E2%80%AFPM.png?alt=media&amp;token=90dc0154-6210-40e7-a66d-e77e793bbeab" alt=""><figcaption></figcaption></figure>

### For You page

The **For You** page is your default project overview. It gives you a quick view of repository health, runs, bugs, and coverage at a glance.

See [For You dashboard](/test-context-manager-documentation/reports-and-analytics/generating-a-report/for-you-dashboard.md) for details.


---

# 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/getting-started/overview/basic-navigation.md?ask=<question>&goal=<user_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.