> For the complete documentation index, see [llms.txt](https://docs.qatts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qatts.com/v-3.0/getting-started-1/dashboard.md).

# Dashboard

The Dashboard in QATTS makes it easy for an user to understand the current status of the testcases.

**Product**: You can select [Product ](https://docs.qatts.com/administration/product)on which you would be performing the testing.

**Code Branch**: You can select or deselect a [Code Branch](https://docs.qatts.com/administration/code-branch) .

**Deployment**:  Select the [Deployment](https://docs.qatts.com/administration/deployment) as per your QA Environment.

**Client:** Select a [Client](https://docs.qatts.com/administration/clients) on which you would be performing the testing.

![](/files/-MjcLvNB52bBOAvJK774)

**All Test Cases Status:** Here you can go through the status of Test cases how many are passed, failed and yet to run.

* **Analyze**: It redirects to Test Result by clients, where you can check status of testcases by client name.

**Functionality Test Cases Status:** Here test cases are segregated according to the functionality names. It shows how many test cases to be run, failed or yet to run.

**Latest 5 Test Cases:** It displays the recent five test cases executed in the application for the selected product.


---

# 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:

```
GET https://docs.qatts.com/v-3.0/getting-started-1/dashboard.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.