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

# Review and Save PR Agent Tests

> Inspect PR Agent results and browser evidence, then save generated tests to a suite in your Test Library.

Check the PR Agent's evidence before you act on a result. Save the generated tests you want to keep. Spur does not add them to your Test Library automatically.

## Read the report on GitHub

Spur posts one comment on the PR and updates it as the run progresses. The first lines show the results, the commit, the deployment, and the Spur environment. Generated tests and existing tests have separate sections. Each failure says what Spur saw. Spur groups errors by cause and says what to do next.

Start with the failures and errors. Then confirm that Spur tested the commit, deployment, and environment you meant to test. To see why Spur chose each saved test, expand **Why Spur picked these tests** under **Existing tests**.

![PR Agent report rendered from a real run, with 2 failed and 21 passed tests in generated and existing test sections and an explanation for each failure](https://mintcdn.com/spur/ik0kTuD3DFwA9eQf/images/pr-agent/github-report-example.png?fit=max\&auto=format\&n=ik0kTuD3DFwA9eQf\&q=85\&s=b450892ea10dd9e389239f2af59ffc9b)

Illustration rendered from a real PR Agent run and styled for readability. The GitHub user is an example.

Each test links to its result. Check the evidence before you decide what to fix.

When saved tests already cover the change, Spur may not generate new ones.

## Open the evidence

Click **Open the PR Agent run**, or click a test in the comment. You need a Spur login to see the evidence.

The run page lists generated tests, existing tests, and any suggested edits. Select a test to see its result.

## Read the evidence

Check what Spur saw, the steps it ran, and any screenshots or recording. A generated test's recording shows Spur creating and checking the test. It is not a separate replay of the saved test.

For example, if the change should keep a user's new role, the evidence should show that role after a refresh. A screenshot of the **Save** click alone does not prove it.

| Result | Meaning | Next step |
| - | - | - |
| Passed | The test's checks passed. | Review the coverage and evidence, then decide whether to merge. |
| Failed | The test did not confirm the expected behavior. | Inspect the evidence. Fix the product, the test expectation, or the test data, then ask Spur to check again. |
| Error | Spur could not finish the test. The behavior is unchecked. | Fix the problem that the comment describes, then ask Spur to check again. |
| Stopped | Spur stopped the test before it finished, for example after a new commit or a stop request. | Ask Spur to test the PR again when you are ready. |
| Waiting or running | The test has no final result yet. | Follow progress in the PR comment or on the run page. |

Saved login tests can appear with the existing tests. Spur runs them before the tests that need them. A login or deployment problem can stop several tests at once.

After a fix, ask in your own words, for example `@spur please recheck the tests that did not pass on the latest preview`. On the run page, **Rerun failed tests** starts the same rerun and takes an optional note. To check the whole change again, describe what you want checked. See [optional guidance](https://docs.spurtest.com/running-tests/cicd/github-agent.md#add-guidance-when-you-need-it).

## Save generated tests

Save tests after the run finishes and you have reviewed it. Spur adds the tests to the Test Suite you select. Saving does not add them to a Test Plan or schedule a run.

**1. Open the save dialog**

At the bottom of the run sidebar, click the save button. Its label shows how many tests you can save, such as **Save 6 generated tests**.

**2. Select and review the tests**

In **Save generated tests**, select the tests you want to keep. Open a test to review its name, steps, URL, and settings. You can edit the open test before you save it.

If you edit a test, save the edits before you open another test. The dialog asks before it discards unsaved edits.

**3. Select the destination suite**

Open **Save to** and select an existing Test Suite. To create one, click **New suite**, enter its name, optionally select a folder, and click **Create suite**.

![Save generated tests footer with the Save to suite selector and the save button](https://mintcdn.com/spur/ik0kTuD3DFwA9eQf/images/pr-agent/save-generated-tests.png?fit=max\&auto=format\&n=ik0kTuD3DFwA9eQf\&q=85\&s=485ced9a5d49625fe35227335a328f97)

Select the destination suite under Save to.

![New suite form in the Save to picker with Name and folder fields](https://mintcdn.com/spur/ik0kTuD3DFwA9eQf/images/pr-agent/save-destination.png?fit=max\&auto=format\&n=ik0kTuD3DFwA9eQf\&q=85\&s=186ca8eb9297fdc3264dd3033e1fa811)

Create a suite in a folder, or select an existing suite as the destination.

Tests belong to suites. If the suite is in a folder, its tests appear in that folder. If the suite has no environment for the test's site, select another suite or add the site to one of the suite's environments.

**4. Save and open the suite**

Click the save button, such as **Save 2 tests**. In the confirmation, click **Open suite** to see the saved tests. You can also find them in the **Test Library**.

You cannot save a test that has no steps. Spur saves unfinished tests as drafts. Finish them before you use them. Saving a failed test does not change its earlier result to a pass.

If only some tests save, the dialog names the ones that failed. Check the suite before you try again, so that you do not save duplicates.

Spur can pick saved tests for later PRs when they are relevant. To run a fixed set regularly, add the tests to a [Test Plan](https://docs.spurtest.com/managing-tests/test-plans/test-plans.md) and set up its runs there.

## Review suggested edits

When a PR changes expected behavior, Spur can suggest an edit to an existing test. The saved test does not change until you edit it.

Click **Review in Spur** in the PR comment. Read **What to change**, **Why**, and the current steps. Click **Edit Test** to make the changes you accept, then save the test. Check the next run's evidence to confirm that the test checks the new behavior.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.