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

# Dry Run

A dry run is a quick execution you use while you are still building a test. It runs the script or suite in a real browser and gives you a full report, but it skips the extras a full test run offers — no visual comparison, no healing, no scheduling.

Use a dry run to answer one question: **does this test actually work?**

## Where you can start one

| From          | How                                                    |
| ------------- | ------------------------------------------------------ |
| A test script | Open the script and click **Dry Run** in the toolbar   |
| A sprint      | Tick a script or suite, then **Execute** → **Dry Run** |
| Test Lab      | Tick a script or suite, then **Execute** → **Dry Run** |

All three open the same run screen.

## What a dry run does not offer

Compared with **Execute Test**, the dry run screen has four options instead of seven. It gives you **Select Browser**, **Database Query**, **Notify Me** and **Verify OTP**. Visual Testing, Healer AI and Schedule Test are only available on a full test run.

## Prerequisites

* A saved test script with at least one step.
* For a sprint, the sprint must be started before **Execute** becomes available.

***

## Running a dry run from a script

1. Open the test script. Click **Dry Run**.

   ![Dry Run button on the script editor](https://239974709-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FycS61vFhJMvvtnJCrDJk%2Fuploads%2Fgit-blob-904d0dec01fc6ac02f966b807bf4f3fafe070ab3%2Frun-dryrun-01.png?alt=media)
2. The run screen opens. Choose where the test should run.

   ![Run screen](https://239974709-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FycS61vFhJMvvtnJCrDJk%2Fuploads%2Fgit-blob-0b37f2405bd2447c632df91123e77d67282b96e7%2Frun-dryrun-02.png?alt=media)

   | Option          | When to use it                                                                                     |
   | --------------- | -------------------------------------------------------------------------------------------------- |
   | **Dedicated**   | Browsers reserved for your account. If you have none, Qyrus tells you where to buy or assign them. |
   | **Shared Pool** | Qyrus's shared browsers. This is the usual choice.                                                 |
   | **Local Run**   | The browser installed on your own machine.                                                         |
3. On **Shared Pool**, pick a **Platform**, then tick a browser.

   ![Shared Pool browsers](https://239974709-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FycS61vFhJMvvtnJCrDJk%2Fuploads%2Fgit-blob-dc728a4410a1c0d660ef847ecef915b53e0705bc%2Frun-dryrun-03.png?alt=media)

   Chrome entries also carry a **Select Device** dropdown if you want to emulate a phone or tablet.

   A note sits above the list: "If selected tests exceed available concurrency, they queue; delays or timeouts occur only if over 30 minutes."
4. Check the **Summary** panel on the right before you run.

   ![Summary panel with a browser selected](https://239974709-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FycS61vFhJMvvtnJCrDJk%2Fuploads%2Fgit-blob-7127d390d472b16a23944ce97ce57a25ca137eee%2Frun-dryrun-04.png?alt=media)

   | Field                           | What it means                                                       |
   | ------------------------------- | ------------------------------------------------------------------- |
   | **Execution parameter file**    | Turn on **Use new feature** if your script is parameterized.        |
   | **Choose environment variable** | Which set of global variables the run uses. Defaults to **Global**. |
   | **Choose screen resolution**    | The window size the test runs at. Defaults to **1024x768**.         |
   | **Executing**                   | How many test scripts are in this run.                              |
   | **Selected Browsers**           | What you picked in step 3.                                          |
5. Click **Run Test**.

   ![Dry run results in the script panel](https://239974709-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FycS61vFhJMvvtnJCrDJk%2Fuploads%2Fgit-blob-c149c576244916c719cb122b8686628d9d007c1a%2Frun-dryrun-05.png?alt=media)

The right-hand panel switches to **Dry Runs** and the new run appears at the top of **Results** with a status of **Run Initiated**. It moves through **Allocating Browser** and **Running** to **Pass** or **Fail**. **Last 5 executions** above the list gives you the recent history at a glance.

## Using a saved run configuration

If someone has already saved a run preset for the project, turn on **Run with configuration** at the top left and choose it instead of setting the options yourself. See [Project Setup](/web-testing/build/projectsetup.md#run-configuration).

***

## Running a dry run from a sprint or Test Lab

1. Open the sprint or Test Lab.
2. Tick the checkbox next to a test suite or a test script. **Execute** stays greyed out until you do. In a sprint it also stays greyed out until the sprint has been started.
3. Click **Execute**, then **Dry Run**.
4. The same run screen opens. Follow steps 2 to 5 above.

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

## Where to find dry run results

Where a dry run shows up depends on where you started it.

| Started from  | Where the result appears                                                                                       |
| ------------- | -------------------------------------------------------------------------------------------------------------- |
| A test script | The **Dry Runs** tab of the script's right-hand panel, as above. It does **not** appear on the report screens. |
| A sprint      | **Sprint Reports** → **Dry Runs** sub-tab.                                                                     |
| Test Lab      | **Test Lab Reports** → **Dry Runs** sub-tab.                                                                   |

The project home page has shortcuts to the last two: under **Analyze**, the **Sprint** and **Test Lab** groups each carry a **Dry Run** button that opens the reports screen with the **Dry Runs** sub-tab already selected.

Click any finished run to open its full report — the same step-by-step view a full run produces. See [Sprint Reports](/web-testing/analyze/sprints.md) for how to read it.

## Where to go next

* [Sprints](/web-testing/run/sprintrun.md)
* [Test Lab](/web-testing/run/testlabrun.md)
* [Reports](/web-testing/analyze/reports.md)