# Mind Maps

* Mind Maps is a Visual Representation of information related to Test Suites using branching.
* It is an hierarchical structure that is used to organize different suites with different test cases under one Project
* Mind Maps helps to track the execution status of test cases. Each node can represent a specific test case, and color-coding or other visual cues can indicate whether a test case has been executed, passed, failed, or is not executed.

It is the feature which is applicable for

* TestLab
* Sprint
* [Tags](/web-testing/analyze/tags.md) - It is used to group all the test cases under the same tag using branching.

***Test Lab***

1. Primary node indicates the ***Project Name*** in case of Test labs.
2. Secondary node indicates the ***Test Suite Name*** .
3. Tertiary node indicates the ***Test Case Name*** .

* Passed Test Case is represented by ***Green***.
* Failed Test Case is represented by ***Red***.
* Not Executed Test Case is represented by ***Orange***

![TestLab\_MindMaps](/files/jKMbm0YxJzjSfFsr6c4e)

***Sprints***

1. Primary node indicates the ***Sprint Name*** in case of Test labs.
2. Secondary node indicates the ***Test Suite Name*** .
3. Tertiary node indicates the ***Test Case Name*** .

* Passed Test Case is represented by ***Green***.
* Failed Test Case is represented by ***Red***.
* Not Executed Test Case is represented by ***Orange***

![Sprint\_MindMaps](/files/N2dGBuBJBLFP2c2kfjzv)

> We have an option to Zoom In and Zoom Out the MindMaps.


---

# Agent Instructions: 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.qyrus.com/web-testing/analyze/mindmaps.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.