Skip to main content
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

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

​
PR-specific checks on existing tests

Existing tests keep their saved steps. For a PR run, Spur can also add up to five temporary checks to each selected existing web test and scenario. The checks apply to that run and its reruns. They do not become part of the saved test. For example, a form restyle can affect a field that an existing test uses to create a plan. The saved flow still creates the plan. An extra check can report whether the typed text stays visible at the end of the step that types it. Spur reviews each new screen that the saved steps show. The checks do not add clicks, scrolling, navigation, or data changes. To check a screen that needs a different path, use a separate test. To ask for a check yourself, name the existing test and describe the check in your comment. For example: @spur please run the saved sign-in test and add a PR check: after sign-in, the homepage shows the left sidebar. If the test uses a Scenario Table, name the scenario too. Spur checks your words as you wrote them. If Spur cannot add the check to that test, it writes a new test for your request instead.

​
Read the check results

In the GitHub comment, expand PR-specific checks to read each check and its evidence. In Spur, select an existing test and open Run result. The PR-specific checks section appears above the saved run result. The PR comment and the run page count check results separately from test results. A saved flow can pass while a required check fails. If the flow passes but a required check stays unverified, Spur reports an error. Check both results before you decide to merge.

​
Limits and reruns

The checks use screenshots only. They cannot prove hidden content, network behavior, exact CSS values, or contrast ratios. Spur does not review a state that appears and goes away between two screenshots. If Spur stops the test or cannot finish the review, it cancels the reviews still in progress. It keeps the problems it confirmed and marks the other checks unverified. A rerun of failed tests also includes tests whose required checks failed or stayed unverified. The rerun keeps the checks from the earlier run. A warning alone does not make Spur rerun a test that otherwise passed.

​
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

Select the destination suite under Save to.

New suite form in the Save to picker with Name and folder fields

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