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

# Sprints

A sprint is a fixed block of time with a goal — the same idea your development team already uses. In Qyrus, a sprint holds the test suites and test scripts you want to run during that period, and keeps a record of how they did.

Use sprints when your testing follows a release cycle. If you just want to run a few tests without the ceremony, use [Test Lab](/web-testing/run/testlabrun.md) instead.

In this guide:

* [Creating a sprint](#creating-a-sprint)
* [Creating a test suite](#creating-a-test-suite)
* [Adding test scripts](#adding-test-scripts)
* [Reusing suites from elsewhere](#reusing-suites-from-elsewhere)
* [Starting the sprint](#starting-the-sprint)
* [Running your tests](#running-your-tests)
* [Editing a sprint](#editing-a-sprint)
* [Finishing the sprint](#finishing-the-sprint)

## Prerequisites

* A project. See [Creating a Project](/web-testing/project-creation/create-project.md).
* At least one test script, so you have something to run. See [Test Scripts](/web-testing/build/creatingscript.md).

***

## Creating a sprint

1. Open your project and click the **Sprints** tile. You can also use **Build** → **Sprints** in the top bar.
2. Click **Create Sprint**.

   ![Sprints page](/files/RgylYS4x4b0QMjxiEMGD)
3. Fill in the **Create Sprint** window.

   ![Create Sprint window](/files/HmECDzk2sf0aJtpw9Imm)

   | Field                       | What to enter                                         |
   | --------------------------- | ----------------------------------------------------- |
   | **Sprint Name**             | A name your team will recognise. Up to 60 characters. |
   | **Sprint Objective**        | What this sprint is for. Up to 255 characters.        |
   | **Sprint Start & End Date** | The sprint's date range.                              |
4. For the dates, click the calendar button and pick a start day, then an end day.

   ![Sprint date picker](/files/68YXTcpvhRL8Vs8clJQr)

   Days before today are greyed out — a sprint cannot start in the past.
5. Click **Create Sprint**. Qyrus opens the new sprint.

   ![New sprint](/files/mSHghFid3Kq7SxjkHMUY)

The sprint starts empty. The next step is a test suite to put your scripts in.

***

## Creating a test suite

A test suite is a named group of test scripts. Suites are how you run several tests in one go — the scripts inside run one after another, in the same browser window.

A suite is not the same thing as a module. A module organises scripts as you build them; a suite can pull scripts from **several** modules together for a run.

1. Click **New Test Suite**. If the sprint already has suites, use the folder button next to the **Test Suites** count instead and choose **Create New Test Suite**.
2. Fill in the **Create Test Suite** window.

   ![Create Test Suite window](/files/hd2uSQC9GJeg5ZqGRkAC)

   | Field                               | What to enter                                                                                           |
   | ----------------------------------- | ------------------------------------------------------------------------------------------------------- |
   | **Suite Name**                      | Up to 60 characters.                                                                                    |
   | **Suite Description**               | Up to 255 characters.                                                                                   |
   | **Auto add test scripts from tags** | Tick this to pull in every script carrying a tag you choose. Leave it clear to build the suite by hand. |

   Tags are set on a script when you create it in the Test Repository. If you create the suite without tags, you get an empty suite and add scripts yourself in the next section.
3. Click **Create Test Suite**.

### Editing or deleting a suite

Click the ⋮ button on the suite card. You get **Edit** and **Delete**.

* **Edit** reopens the suite window with the current name and description filled in. Change them and click **Update Suite**.
* **Delete** asks you to confirm, then removes the suite.

***

## Adding test scripts

1. Click **Import Scripts**.
2. The **Import Scripts** screen has two halves. On the left is your **Test Repository**; on the right is the **Test Suite** you are filling. Click a module on the left to see its scripts.

   ![Import Scripts screen](/files/xuOyQutm1cSb3BNNLPV9)
3. Choose the scripts you want. Any of these work:
   * Tick the checkbox next to a script name.
   * Tick **Select all Test Scripts** to take the whole module.
   * Click the **+** button on a script.
   * Drag a script across to the right-hand pane.
4. Click **Push to Suite**. The scripts move to the right-hand pane.

   ![Scripts staged in the suite](/files/MOW2q4yAG838WuDJuO9j)
5. Click **Save to Suite**. Qyrus confirms with "Test Scripts imported successfully" and returns you to the sprint.

The **Test Scripts** counter at the top of the sprint updates to show what the suite now holds.

***

## Reusing suites from elsewhere

You do not have to rebuild a suite you already have. Click the folder button next to the **Test Suites** count. Besides **Create New Test Suite**, it offers:

| Option                   | What it does                                                            |
| ------------------------ | ----------------------------------------------------------------------- |
| **Import From Sprint**   | Copies a suite from another sprint — active or not yet started.         |
| **Import From Test Lab** | Copies a suite you built in [Test Lab](/web-testing/run/testlabrun.md). |

Either way, pick the source, tick the suite you want, and confirm. The suite count on the left updates and the imported suite's scripts appear in the middle of the screen.

***

## Starting the sprint

A sprint has to be started before you can run anything in it.

1. Open the sprint and click **Start Sprint**, top right.
2. Check the details and click **Start Sprint** again to confirm.

   ![Start Sprint confirmation](/files/TM1RdVN5GejtWd6XqkHc)
3. The button changes to **Finish Sprint**, and a counter below it shows how many days are left.

   ![A running sprint](/files/fCkUMqVMwbETubRtkRPo)

Until you do this, **Execute** stays greyed out. Hovering it explains why: "To Execute the script please start the sprint".

***

## Running your tests

1. Tick the checkbox next to a test suite or an individual test script. To run everything, use the checkbox next to the **Test Suites** or **Test Scripts** count.

   ![Selecting a script to run](/files/xTBua84iAJwgrU6WTKUl)

   To look at a script before you run it, click its name. That opens the script's steps, where you can check or edit them and save. Use your browser's back button to return to the sprint.
2. **Execute** becomes available. Click it.
3. Choose the kind of run.

   ![Execute menu](/files/vBW3KPmoRrqVFyVO8cxC)

   | Option           | What it is                                                                                   |
   | ---------------- | -------------------------------------------------------------------------------------------- |
   | **Dry Run**      | A quick check that the test works. Fewer options. See [Dry Run](/web-testing/run/dryrun.md). |
   | **Execute Test** | A full run, with visual testing, healing and result sharing available.                       |
4. Either choice opens the run screen. Set your options down the left, check the **Summary** panel on the right, then click **Run Test**.

   ![Execute Test run screen](/files/blXJtLOjxtV5gHT6jVWl)

   A sprint run offers these tabs:

   | Tab                | What it is for                                                                                                                               |
   | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------- |
   | **Select Browser** | Where the test runs — **Dedicated**, **Shared Pool** or **Local Run**. Required.                                                             |
   | **Visual Testing** | Compares layout and content against a baseline. One script at a time. See [Visual Testing](/web-testing/advanced-features/visualtesting.md). |
   | **Database Query** | Pick a saved database connection, if your steps read from one.                                                                               |
   | **Notify Me**      | Email the result to yourself or to others.                                                                                                   |
   | **Healer AI**      | Lets Qyrus repair locators that have changed. See [Healer AI](/web-testing/advanced-features/healer.md).                                     |
   | **Verify OTP**     | Turn on if the script has to handle a one-time password.                                                                                     |

   Scheduling is not offered here. To schedule a run, use [Test Lab](/web-testing/run/testlabrun.md).
5. Qyrus confirms the run has started.

   ![Execution Started](/files/R60KddW5Rjb3SHEE0Lpx)

   * **Go Back** returns you to the sprint.
   * **Go To Reports** opens [Sprint Reports](/web-testing/analyze/sprints.md), where you can watch the run progress and read the result.

**A suite run produces two rows, not one.** Running a suite with a single script inside reports **2 Test Scripts** — one row for the suite, one for the script. The report counters count both, so a single execution shows **Total Execution 2**. Nothing ran twice.

***

## Editing a sprint

1. Click the pencil button next to the sprint name.
2. Change the name or the objective and click **Update Sprint**.

   ![Edit sprint](/files/opgBeDaNqBZa0ZZUgxjY)

The date range cannot be changed. It is fixed when the sprint is created, whether or not the sprint has been started.

***

## Finishing the sprint

When the sprint's testing is done:

1. Click **Finish Sprint**, top right.
2. Review the summary — test suites, test scripts, how many ran and how many did not — and click **Finish Sprint** to confirm.

   ![Finish Sprint](/files/dTSO34wVz5WRABVe52lZ)

The button changes to **Sprint Completed**. **A completed sprint is read-only**: you cannot run any script or suite in it again. Its reports stay available under **Previous Sprints** in [Sprint Reports](/web-testing/analyze/sprints.md).

## Where to go next

* [Dry Run](/web-testing/run/dryrun.md)
* [Test Lab](/web-testing/run/testlabrun.md)
* [Sprint Reports](/web-testing/analyze/sprints.md)