> 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/sprints.md).

# Sprint Reports

Sprint Reports is where you read the results of everything run inside a sprint — how the sprint is tracking overall, which suites are passing, and what happened step by step in any single run.

## Opening Sprint Reports

Open your project, then in the **Analyze** group click **Reports** under **Sprint**.

![The Sprint buttons in the Analyze group](/files/VxcLV7z35NSQH2YJJeIu)

Once you are inside the project you can also use the **Reports** menu in the top bar and choose **Sprints**. Both routes land on the same screen.

The screen opens on **Active Sprints**. **Previous Sprints** holds sprints you have finished. Use **Select Sprint:** to switch between sprints, and watch **Active Runs** in the top right to see how many runs are going on right now.

There are five tabs: **Sprint Dashboard**, **Sprint Detail**, **Dry Runs**, **Executions** and **Performance**. [Test Lab Reports](/web-testing/analyze/testlab.md) has the same five in a different order, so check which screen you are on before deciding a run has vanished.

## Sprint Dashboard

The dashboard answers "how is this sprint going?" in one screen.

![The Sprint Dashboard](/files/uW4v3NgOwbcuXDoHWpe2)

| Panel                                     | What it tells you                                                        |
| ----------------------------------------- | ------------------------------------------------------------------------ |
| Sprint header                             | The sprint's status, **Start time**, **End time** and **Days remaining** |
| **Test Suites** / **Test Scripts**        | How much is in the sprint                                                |
| **Daily test executions**                 | Runs per day, so you can see whether testing is actually happening       |
| **Most Executed test script**             | The script run most often, with its pass rate                            |
| **Overall tests executed in the sprints** | Total runs, split into **Passed** and **Failed**                         |
| Browser breakdown                         | How many runs went to Google Chrome, Mozilla Firefox and Microsoft Edge  |

The panel beside **Most Executed test script** groups the sprint's scripts by tag. When it has nothing to show it reads "No tags found in scripts for selected sprint". See [Tags](/web-testing/analyze/tags.md) for what tags are and how to add them.

## Sprint Detail

Sprint Detail is the pass-rate view — one row per suite, with the scripts inside it.

![The Sprint Detail tab](/files/OITfAfEbbed4n3JY4Qm1)

| Column                        | Meaning                                                |
| ----------------------------- | ------------------------------------------------------ |
| **Test suite / Test scripts** | The name of the suite or script                        |
| **Total Execution**           | How many times it has run                              |
| **Total Pass**                | How many of those runs passed                          |
| **Total Fail**                | How many failed                                        |
| **Last 5 Executions**         | The result of each of the last five runs, newest first |
| **Pass %**                    | The overall pass rate                                  |

Click the arrow at the end of a suite row to see the scripts it contains, and the arrow on a script row to see each individual run — **Executed on**, **Execution time**, **Platform**, **Browser**, **Status** and the browser **Version**.

![A suite and a script expanded](/files/keqhjn0Fk7WU6SvxmgX8)

Running a suite counts as more than one execution: the suite gets a row and so does each script inside it. A suite holding one script therefore shows **Total Execution 2** after a single run.

## Executions

Executions is the full history of everything run in the sprint.

![The Executions tab](/files/pUfncWiet6OevjYXLEOb)

| Column             | Meaning                        |
| ------------------ | ------------------------------ |
| **Test scripts**   | The script or suite that ran   |
| **Executed on**    | Date and time of the run       |
| **Execution time** | How long it took               |
| **Platform**       | The operating system it ran on |
| **Browser**        | The browser it ran in          |
| **Status**         | **Pass** or **Fail**           |

Use **Search Executed Runs** to find a run by name, and **Refresh** to update the statuses of runs still going. **Delete All** clears the whole list.

Three icons sit between **Browser** and **Status** on a finished run: **Video** plays the recording, and **Healer** opens what Healer AI did. A run still in progress shows fewer of them.

### The row menu

Click the **⋮** on any row for five actions.

![The row menu on an execution](/files/kWZP2zDE35r9kg8cl1oP)

| Action              | What it does                                    |
| ------------------- | ----------------------------------------------- |
| **Download Report** | Downloads the report for that run               |
| **Mail Report**     | Emails the report to addresses you enter        |
| **Retry**           | Runs it again, as a new entry in the list       |
| **Create Ticket**   | Raises a ticket in your connected issue tracker |
| **Delete**          | Removes that report                             |

## Reading a single run

Click the arrow at the end of a row to open the **Run Result** — the step-by-step story of that run.

![A run result for a single script](/files/j4vkHKEyB3pFqh94KVX4)

The tiles across the top give **Test Cases**, **Passed Tests** and **Failed Tests**. Beside them are the conditions the run used — operating system, browser and version, environment and screen resolution. Last come the timings: the date, **Execution Time**, **Start time** and **End time**.

Below that, the **Test Report** tab lists every step: **Step Description**, **Expected Output**, **Actual Output**, **Data** and **Status**, with **Test Case Execution :** giving the time for the script as a whole. The icon at the end of each step row opens the screenshot taken at that moment.

Open a **suite** run instead and the same screen shows each script in the suite in turn, with its own steps and its own execution time.

![A run result for a suite](/files/RhxLdPfJAZT3HPVvOdbw)

### The toolbar

Five buttons sit under the run name.

![The run result toolbar](/files/pmfYoMElUgFXMYNUR1fM)

| Button                  | What it does                                               |
| ----------------------- | ---------------------------------------------------------- |
| **video**               | Plays the recording of the run                             |
| **Mail Report**         | Emails the report                                          |
| **Download Report**     | Downloads the report                                       |
| **Performance Metrics** | Shows how long the pages and files in the run took to load |
| **Download PDF**        | Downloads the report as a PDF                              |

### Performance Metrics

**Performance Metrics** opens **Performance Metrics Preview**, a record of the files the browser loaded while the test ran and how long each one took.

![The Performance Metrics Preview](/files/k7pgmbj0YeBefQzMY1Ko)

It is raw data rather than a chart. Each entry names a file and gives its timings in milliseconds. **Download Metrics** saves the whole set, which is the practical way to use it — open the saved file in a spreadsheet or hand it to a developer.

Every run records this and you do not have to turn anything on — executions and dry runs alike, whether they came from a sprint or from Test Lab. It is not the same thing as the **Performance** tab described below.

### Console Logs

The **Console Logs** tab, next to **Test Report**, shows what the browser itself logged during the run — timestamped and numbered. It is the first place to look when a step failed for a reason the report does not explain.

![The Console Logs tab](/files/SNWYcCAekpsVPUwbZxvA)

## Dry Runs

The **Dry Runs** tab lists dry runs started from inside the sprint. They are kept apart from ordinary executions, so check this tab if a run you expected is missing from **Executions**.

![The Dry Runs tab](/files/4Uqppkh8jV8zgrO73zY4)

The columns and the row **⋮** menu are the same as on Executions. The search box here is **Search Dry Run Report...**.

![The row menu on a dry run](/files/12TG2xiXukSTSx1qkKCk)

Until you run one, the tab reads "No Dry Run Reports for selected Sprint". See [Dry Run](/web-testing/run/dryrun.md) for how to start one.

## Performance

The **Performance** tab lists **performance runs**. It is not where you find the timings for an ordinary execution — those are on the run result itself, under [Performance Metrics](#performance-metrics).

| Column                        | Meaning                         |
| ----------------------------- | ------------------------------- |
| **Test Scripts**              | The script that ran             |
| **Total Simulations**         | How many times it was executed  |
| **Start Time** / **End Time** | When the run began and finished |
| **Executed By**               | Who started it                  |
| **Status**                    | The result                      |

**Refresh** updates the statuses, and the icon at the end of a row deletes that report.

![The Performance tab](/files/ziNa9fPHEWXazQ5qqxnz)

Click the arrow at the end of a row for the detail of each execution — **Number**, **Executed On**, **Execution Time** and **Status**.

![A performance run expanded](/files/eO0tLk4rUNsJmMmilQTo)

If your **Performance** tab is empty, no performance run has been recorded for the sprint you have selected. An ordinary execution and a dry run do not produce one, and there is no performance option on the **Execute Test** or **Dry Run** configuration screens — so on most projects this tab stays empty. For the timings of a run you have already done, use **Performance Metrics** on the run result instead.

## Previous Sprints

Click **Previous Sprints** for the sprints you have already finished, each with its description, status and start date.

![The Previous Sprints tab](/files/p03NHRylMinxl2pPl7YG)

## Why Execute might be greyed out

You cannot start a second run while one is still going. The **Execute** button on the sprint stays disabled until the run in progress finishes — watch **Active Runs** in the top right of the report screen to see when it clears. [Dry Run](/web-testing/run/dryrun.md) covers the other reasons the button can be unavailable.