> 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** is where you read the record of a run — what ran, when, on which browser, whether it passed, and what happened at each step. Runs started from a sprint or from Test Lab are recorded here; a dry run started from inside a script is not.

Reports cover the two places tests run: **Sprints** and **Test Lab**. Alongside them sit the **Mind maps**, which show the same tests as a picture rather than a table.

## The eight report screens

Open your project, and the **Analyze** group on the project home page lists everything reports can show you. The **Reports** tile on the left describes the group; the buttons beside it are what you click.

![The Analyze group on the project home page](/files/sc0M507n6YfOLggu8kfY)

| Group         | Button         | What it shows                                                                      |
| ------------- | -------------- | ---------------------------------------------------------------------------------- |
| **Sprint**    | Reports        | Dashboard, per-suite detail, execution history and performance for a chosen sprint |
|               | Dry Run        | Dry runs started from inside a sprint                                              |
| **Test Lab**  | Reports        | The same set of screens for Test Lab runs                                          |
|               | Dry Run        | Dry runs started from Test Lab                                                     |
|               | Scheduled Runs | Runs waiting to happen, and the schedules that trigger them                        |
| **Mind maps** | Sprint         | A sprint drawn as a tree of suites and scripts                                     |
|               | Test Lab       | The project's Test Lab suites drawn the same way                                   |
|               | # Tags         | Scripts grouped by the tags you gave them                                          |

The **Sprint → Reports** and **Test Lab → Reports** buttons each open a screen with five sub-tabs, so most of what you need is behind those two.

## The Reports menu in the top bar

You do not have to return to the project home page every time. On the working screens — the test repository, a script, another report — the top bar carries a **Reports** menu. The project home page itself does not have it.

![The Reports menu in the top bar](/files/KbBaiRxR4y9hPrOy8z57)

| Menu item          | Opens                      |
| ------------------ | -------------------------- |
| **Sprints**        | Sprint Reports             |
| **Test Lab**       | Test Lab Reports           |
| **Scheduled Runs** | The list of scheduled runs |

Mind maps are not in this menu. Open them from the project home page.

## Open your project first

Report screens read from the project you currently have open. If a report screen comes back blank, check that you have a project open: click **All Projects** in the breadcrumb at the top of the screen, open your project, and try again.

## Where to go next

| To read about                                        | Go to                                               |
| ---------------------------------------------------- | --------------------------------------------------- |
| Sprint reports, dry runs and performance             | [Sprint Reports](/web-testing/analyze/sprints.md)   |
| Test Lab reports, scheduled tests and scheduled runs | [Test Lab Reports](/web-testing/analyze/testlab.md) |
| The tree view of sprints and Test Lab                | [Mind Maps](/web-testing/analyze/mindmaps.md)       |
| Grouping scripts by tag                              | [Tags](/web-testing/analyze/tags.md)                |