# Run manual tests with the Test Wizard

Source: https://docs.qualflare.com/docs/runs/manual-testing · Last updated: 2026-10-27

Run manual tests in Qualflare: start a launch from suites or a test plan, then record Passed, Failed, Blocked or Skipped for each case in the Test Wizard.

To run manual tests in Qualflare, start a launch from suites with **Start Launch**, or from a saved test plan with **Create Run**, and record one verdict per case in the [Test Wizard](https://docs.qualflare.com/docs/reference/glossary#test-runner-wizard); you need the Editor role or higher on the project.

## Before you begin

* (requires the Editor role or higher in the project) ([Roles and permissions](https://docs.qualflare.com/docs/administration/roles-permissions#workspace-and-project-roles))
* Suites that contain cases ([Test suites](https://docs.qualflare.com/docs/test-management/test-suites)), or a [test plan](https://docs.qualflare.com/docs/test-management/test-plans)
* At least one environment ([Environments](https://docs.qualflare.com/docs/runs/environments)). New projects start with four.

Anyone with the Editor role or higher on the project can record verdicts in, and finalize, any manual launch of the project, so a team can share one run.

## Start a launch from suites

Start a launch from suites when you want to run every case in them.

### Step 1: Open Start Launch

Click **Launches** in the project sidebar, then click **Start Launch**.

### Step 2: Choose the suites

Select one or more suites (up to 100), then click **Next**. Every case in the selected suites is included.

*Figure: Step 1 of Start Launch: choose the suites to run. Every case in them is included.*

### Step 3: Set up the launch

| Setting         | Required | Notes                                                                                                          |
| --------------- | -------- | -------------------------------------------------------------------------------------------------------------- |
| **Environment** | Yes      | Where you are testing                                                                                          |
| **Language**    | Yes      | Defaults to en-US                                                                                              |
| **Platform**    | Yes      | Web, Android or iOS. Defaults to Web                                                                           |
| **Branch**      | No       | The branch under test, up to 128 characters                                                                    |
| **Milestone**   | No       | Links the launch to a [milestone](https://docs.qualflare.com/docs/test-management/milestones)                  |
| **Name**        | No       | Names the test plan Qualflare creates for this run, up to 128 characters. Defaults to `Launch – <date> <time>` |

Completed milestones aren't listed. The **Milestone** field lists only the open milestones among the project's first 10 milestones by number, so a newer milestone may be missing from it.

*Figure: Step 2: Environment and Language are required, and Platform defaults to Web.*

### Step 4: Start the launch

Click **Start**. Qualflare shows `Launch #<seq> started`, creates a test plan with the selected cases and opens the Test Wizard.

You should see the launch as **Pending** on **Launches** until you finalize it.

> **Warning:** Environment and language can't be changed once the launch exists. With **Create Run**, they lock at your first verdict, so check both before you record it. A launch you started with **Start Launch** uses the environment and language you chose in its dialog. The **Environment** and **Language** columns on the **Launches** page show a launch's values.

## Run a test plan

A test plan is a saved set of test cases you run together, such as a regression pass. Plans have no schedule and no assigned testers. You start each run by hand.

### Step 1: Click Create Run

Click **Test Plans** in the project sidebar, then click the **Create Run** (play) button on the plan's row. The Test Wizard opens.

### Step 2: Check the environment and language

Select these before the first verdict:

* **Environment**: the deployment environment being tested, such as staging or production. The wizard preselects the first environment in its list, so check it.
* **Language**: the locale for this test run. The wizard preselects en-US.

You can't record a verdict until both are set.

### Step 3: Record the first verdict

Qualflare creates the launch when you record the first verdict. From then on, the environment and language are locked.

## Record verdicts

You record verdicts with the four buttons at the bottom of the case detail panel, one verdict per case:

| Verdict | When to use                                               |
| ------- | --------------------------------------------------------- |
| Passed  | The case executed as expected                             |
| Failed  | The case did not produce the expected result              |
| Blocked | The case could not be executed due to an external blocker |
| Skipped | The case was intentionally not executed                   |

Qualflare saves **Blocked** as Aborted. Launch results and charts show it as Aborted.

*Figure: Record one verdict per case. Blocked is saved as Aborted.*

When you click **Failed**, the **Mark as Failed** dialog opens. Describe what went wrong, then click **Mark as Failed**. The description is optional, but it is what your team sees on the case run.

*Figure: Failed opens Mark as Failed. The description is optional, and your team sees it on the case run.*

To change a verdict before you finalize, select the case and click a different verdict. You can't attach files or add comments in the wizard. After you submit a verdict, the wizard moves to the next pending case.

### Find your way in the wizard

The wizard has two panels. Above them, a progress bar counts **Passed**, **Failed**, **Blocked**, **Skipped** and **Pending** cases.

* **Left panel, the case list:** all test cases from the plan, grouped by suite, each with a status icon (pending, passed, failed, blocked, skipped).
* **Right panel, the case detail:** the selected case's number, name, priority, suite and description, and its numbered steps. Steps are read-only: you record one verdict for the whole case. Shared steps appear as expandable sub-step groups.

Use the &#x2A;*←*&#x2A; and &#x2A;*→** buttons at the bottom to move between cases, or click any case in the left panel to jump directly to it.

*Figure: The Test Wizard shows one case at a time, with its steps and a timer.*

### Search cases

Use the search bar in the left panel to find specific cases by name or sequence number. This is useful for large test plans.

### Time each case

The timer measures each case on its own. It starts when you open a case, starts over when you move to another case, and stops when you record a verdict. The time is saved as that case's duration. To pause it, for example during an interruption, click the pause button next to the timer.

## Finalize the launch

Finalize the launch once every case has a verdict. A banner then appears: "Run complete. All N cases executed — ready to finalize." **Finalize Launch** appears only then. Click it. Qualflare confirms with "Manual test run completed successfully!" and takes you to the **Launches** list. Open the launch there to see the full results.

Until you finalize, the launch stays **Pending**. To resume a run, click the **Pending** launch on **Launches**.

A manual launch doesn't start AI launch analysis, failure clustering, Slack or webhook notifications, and doesn't appear on a public report.

*Figure: When every case has a verdict, finalize the launch to move it out of Pending.*

## Delete an in-progress run

> **Caution:** Deleting an in-progress launch is permanent. All recorded verdicts are lost, and there is no undo.

If you need to abandon the run, click the &#x2A;*⋯** menu and select **Delete launch**, then confirm in the **Delete Launch** dialog. The menu appears once the launch exists.

## Troubleshoot

* **The wizard shows `Select environment and language first`**: set **Environment** and **Language** above the case list, then record the verdict.
* **Start Launch fails with `selected suites contain no cases`**: pick suites that have cases.
* **A verdict or Finalize Launch fails with `launch is no longer accepting submissions` or `launch has already been completed`**: a teammate finalized the launch. Open it from **Launches** to see its results.
* **The locked Environment shows another value**: when the wizard reopens a launch, its locked selectors can show the first environment and en-US. Check the **Environment** column on **Launches**, which shows the launch's own value.

## Next steps

* [Analyze launch results](https://docs.qualflare.com/docs/runs/analyze-results): read the launch's success rate and open its failed case runs.
* [Case runs](https://docs.qualflare.com/docs/runs/launches#case-runs): the result each case gets in a launch.
* [Share and export results](https://docs.qualflare.com/docs/runs/share-results): publish a report or get launches as JSON.
* [Shared steps](https://docs.qualflare.com/docs/test-management/shared-steps): the expandable step groups some cases show.
* [Create, triage and close defects](https://docs.qualflare.com/docs/defects/manage-defects): track the bugs a run finds.