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.
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 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.
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 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.
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.
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.
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.
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.
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.
The toolbar
Five buttons sit under the run name.
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.
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.
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 columns and the row ⋮ menu are the same as on Executions. The search box here is Search Dry Run Report....
Until you run one, the tab reads "No Dry Run Reports for selected Sprint". See Dry Run 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.
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.
Click the arrow at the end of a row for the detail of each execution — Number, Executed On, Execution Time and Status.
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.
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 covers the other reasons the button can be unavailable.
Last updated