> ## Documentation Index
> Fetch the complete documentation index at: https://docs.spurtest.com/llms.txt
> Use this file to discover all available pages before exploring further.
> ## Agent Instructions
> Spur is an AI-powered QA engineer that lets teams create and run automated end-to-end tests for web and mobile apps using natural language.
> When answering questions about Spur, cite the relevant page from docs.spurtest.com.
# Test plan review
> Walk through every failure, warning, and error in a test plan run in Spur, triage each result, group by cause, and rerun failing tests without leaving the page.
After running a test plan, the review flow gives you a guided way to work through every failed test, warning, and error. You can triage each result, add notes, edit tests inline, create bug tickets, export PDFs, and pick up exactly where you left off across sessions.
## Starting a review
Open a test plan run from the run history. At the top of the results page you'll see the **Test Review** progress bar, which shows the number of tests remaining to review. This count includes failures, warnings, and errors.
Click **Start** to enter the review flow.
## The review interface
The review flow is split into two panels:
* **Left panel** — A list of all tests that failed, surfaced a warning, or encountered an error in this run
* **Right panel** — Full details for the selected test: failure reason, steps, screenshots, video, and console and network logs
Work through tests one at a time. As you assign a status to each test, it moves to the **Reviewed** tab. The left panel updates automatically so you always know what's left.
### Grouping the test list
Use the **Group by** dropdown at the top of the left panel to change how tests are organized:
* **Failure Reason** (default) — tests grouped by the root cause Spur detected
* **Folder + Suite** — tests grouped by folder, with a second level for each suite inside it
* **Environment** — tests grouped by the environment they ran against
* **Scenario** — tests grouped by scenario when the plan uses a scenario table
Your selection is saved in the URL, so sharing a link preserves the grouping for whoever opens it.
Use the **Expand all** and **Collapse all** control next to the dropdown to open or close every group at once — useful for scanning a large review list.
## Classifying tests
To assign a status, press C or click **Classify** in the action bar at the bottom of the screen. This opens the classify modal with four options:
**Bug** — Mark this when you have found a bug in your application.
**Closed** — Use this when the failure was expected or explained — for example, a deployment was in progress or the test environment was temporarily unavailable.
**Needs Rework** — Use this when the test steps themselves need to be updated. You can edit the test inline from within the review flow (see [Editing and rerunning tests](#editing-and-rerunning-tests) below).
**Needs Investigation** — Use this when you need more context before deciding — for example, you want to discuss the failure with a teammate before committing to a status.
You can quick-classify by pressing 1 through 4 while the classify modal is open.
The Reviewed tab groups tests into **Resolved** (Bug and Closed) and **Unresolved** (Needs Rework and Needs Investigation). Resolved tests are considered dealt with; unresolved tests still require follow-up action.
## Adding notes
You can attach a note to any test to record context, observations, or next steps.
* **Standalone note** — Press N or click **Note** in the action bar. Type your note and submit. Notes appear in the test timeline.
* **Note with classification** — While the classify modal is open, hold Shift and press a number key (Shift+1 through Shift+4) to assign a status and add a note at the same time.
Notes can also be added to multiple tests at once when using [bulk selection](#bulk-actions).
## Undo
Every classification action can be undone. After you classify a test, a toast notification appears with an **Undo** button. You can also press Cmd+Z (Mac) or Ctrl+Z (Windows/Linux) to revert the last action.
Undo restores the previous review status, removes any note that was created with the action, and returns you to the previous tab and selected test.
## Bulk actions
You can select multiple tests and apply actions to all of them at once.
1. Use the checkboxes in the left panel to select individual tests, or use the group-level checkbox to select all tests in a group.
2. The action bar changes to show the number of selected tests with a blue highlight.
3. From here you can:
* **Bulk classify** — assign the same status to all selected tests
* **Bulk notes** — add a note to all selected tests
* **Bulk PDF export** — export results for all selected tests
* **Bulk ticket creation** — create tickets for all selected tests
Press Escape to clear the selection.
## Keyboard shortcuts
The review flow supports keyboard shortcuts for fast triage.
| Shortcut | Action |
| - | - |
| C | Open or close the classify modal |
| 1 – 4 | Quick-classify (Bug, Closed, Needs Rework, Needs Investigation) when the classify modal is open |
| Shift+1 – Shift+4 | Classify with a note |
| N | Open the note input |
| S | Open the share menu |
| ← / → | Navigate to the previous or next test |
| Cmd/Ctrl+Z | Undo the last action |
| Escape | Clear bulk selection |
## Editing and rerunning tests
You can fix a test and re-run it without leaving the review flow:
With a test selected in the right panel, click **Edit**. The test side peek opens so you can update the steps.
Click **Save and Run**. A confirmation modal appears before the run starts. Spur saves your changes and triggers a new run.
A banner appears at the top of the panel showing when the test was edited and the rerun status. Once the rerun finishes, you'll see whether it passed or failed — giving you more context to finalize the status.
You can also open the **Run History** tab in the right panel to see all previous runs for the selected test in the same configuration (environment, browser, viewport).
### Rerunning native (mobile) tests
When you rerun a native test from the review flow, Spur automatically uses the correct native platform configuration from the original run. The run modal opens pre-configured with the matching platform (iOS, Android, or both) and environment, skipping directly to the summary step.
This means:
* **Web tests** rerun with the original browser and viewport
* **Native tests** rerun with the original native platform — no browser or viewport is applied
The rerun inherits the same environment and scenario configuration as the original test run. If the original test ran on Android with a specific environment, the rerun uses the same settings.
## Creating tickets
From within the review flow, you can file a Jira ticket, a Linear issue, or an Azure DevOps work item for any test:
Click **Share** in the action bar (or press S) and select **Create a Ticket**.
Spur pre-populates the ticket with a failure reason, reproduction steps, test execution details, and a direct link to the test run. Edit any of these fields as needed.
Choose the project, priority, and assignee.
Click **Create Ticket**, or **Create Work Item** for Azure DevOps. The ticket identifier appears next to the test in the Reviewed tab, with a ticket icon to identify it at a glance.
A ticket integration must be connected before you can create tickets from the review flow. Only the connected trackers appear as options. See the [Integrations guide](/analysing-tests/integrations/integrations) for setup.
## Emailing review results
Once a run has been reviewed, you can send a summary email to configured recipients or to a one-off address. The email shows the total runs, the classification breakdown, the reviewer's name, and highlights the tests classified as bugs.
You can send the email from three places:
* The Test Plan run page — use the **Email** button in the header.
* The end of the review flow — click **Email Results** on the completion screen.
* The top-right header inside the review flow — available once every test has been reviewed.
In the send dialog:
* Recipients set to **After review** in the Test Plan's [email alerts](/running-tests/test-plans#email-alerts) are selected by default.
* Add any one-off address by typing it in — the recipient does not need to be configured on the Test Plan.
* You can resend the email to someone who has already received it.
Recipients set to **On finish** get their email automatically when the run reaches a terminal state and are not part of the manual send.
## Exporting to PDF
You can export test results as PDF reports from the share menu:
* **Single test** — Click **Share** and select **Export PDF** to download a report for the currently selected test.
* **Multiple tests** — Select tests using [bulk selection](#bulk-actions), then use **Share** to export all selected tests in a single bulk PDF.
## Saving progress and resuming
You don't have to finish a review in one session. Click **Exit** at any time — your progress is saved automatically.
When you return to the test plan run page, the progress bar converts to a summary table showing all reviewed tests grouped by status. Tests with linked tickets show a ticket icon. You can re-enter the review flow from the summary to continue with the remaining tests.
The goal of the review flow is to reach zero unreviewed tests: every failure, warning, and error has been triaged so nothing slips through before a release.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.