> For the complete documentation index, see [llms.txt](https://docs.qyrus.com/web-testing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qyrus.com/web-testing/analyze/reports.md).

# Reports

Reports are essential documents that provide comprehensive information about the testing process. Report provides the details of execution of test cases, including which tests were run, their status (Pass, Fail,Aborted), and any defects or issues encountered during testing with execution time. It offers a snapshot of the current state of testing.

A report provides an overview of the entire testing effort. It includes statistics on the number of test cases executed, Pass/Fail rates, test coverage, and any outstanding defects.

Qyrus furnishes comprehensive reports for the Test Scripts executed within the Sprints and Test Lab sections. Furthermore, it offers a structured hierarchy for Mind Maps and Tags, enhancing the organization and accessibility of relevant information.

For more informaton on Sprint Reports can refer this [SprintsReports](/web-testing/analyze/sprints.md)

For more informaton on Test Lab Reports can refer this [TestLab](/web-testing/analyze/testlab.md)

For more informaton on Mind Maps can refer this [MindMaps](/web-testing/analyze/mindmaps.md)

For more informaton on Tags can refer this [Tags](/web-testing/analyze/tags.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://docs.qyrus.com/web-testing/analyze/reports.md?ask=<question>&goal=<endgoal>
```

`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.