# Tutorial: run a manual regression cycle

Source: https://docs.qualflare.com/docs/get-started/manual-test-cycle · Last updated: 2026-10-28

Run a manual regression cycle in Qualflare: write cases with steps, save them as a test plan, run it in the Test Wizard, then finalize it and file defects.

To run a manual regression cycle in Qualflare, save a suite's cases as a test plan, click **Create Run** on it for each release and record a verdict per case in the Test Wizard; you need the Editor role or higher in the project.

This tutorial uses a suite called `Checkout` with three cases, run once for release 2.4 and again for 2.5.

## Before you begin

* Requires the Editor role or higher in the project.
* A project. New to Qualflare? Start with [Create your account and workspace](https://docs.qualflare.com/docs/get-started/create-account).
* Test plans: (available on Starter, Core, Scale, Enterprise, Open Source). A Starter workspace holds up to 10 test plans.
* Shared steps, for the optional last action of [Write the cases](https://docs.qualflare.com/docs/get-started/manual-test-cycle#write-the-cases): (available on Core, Scale, Enterprise, Open Source)

## Write the cases

1. In the project sidebar, click **Browse**, then **Create Suite**. Enter the **Name** `Checkout` and a **Description**, which the suite needs, then click **Create**.

   *Figure: Start the cycle in Browse: a new project has no suites until you create one.*

2. Click the suite, open its **Test Cases** tab and click **Create Case**. Enter a **Name** such as `Pay with a saved card` and click **Create**. Add the other cases the same way. The dialog saves only the name; set the priority on the case afterwards ([Create and edit test cases](https://docs.qualflare.com/docs/test-management/create-test-cases)).

   *Figure: The Create Case dialog saves only the name; set the other fields on the case afterwards.*

3. Open a case's **Steps** tab and click **Create Step**. Write one action per step, and write what a pass shows as a step of type **Expected Result**.

   *Figure: Record what a passing test shows as a step of type Expected Result.*

4. Optional: for steps many cases share, such as signing in, create a [shared step](https://docs.qualflare.com/docs/test-management/shared-steps) once and add it to each case with **Insert Shared Step** on its **Steps** tab. The list shows only the project's first 10 shared steps by number, so a newer shared step may be missing from it.

## Save the cases as a test plan

1. Click **Test Plans**, then **Create Test Plan**. Enter a **Name**, such as `Checkout regression`, and a **Description**, then click **Create**.
2. Open the plan, go to its **Test Cases** tab, tick the `Checkout` suite to add all of its cases, and click **Save Cases**.

> **Warning:** A run of the plan includes only the cases on its **Test Cases** tab. Saved queries on its **Dynamic Queries** tab add no cases to the run.

## Run the plan

1. On **Test Plans**, click **Create Run** (the play button) on the plan's row. The Test Wizard opens.
2. Check **Environment**, for example `staging`, and **Language** at the top before your first verdict. Both lock when you record it, and that is when Qualflare creates the launch.
3. For each case, follow its steps and click **Passed**, **Failed**, **Blocked** or **Skipped**. **Failed** opens **Mark as Failed**: describe what went wrong, then click **Mark as Failed**. Qualflare saves **Blocked** as Aborted.
4. Testers can share the run: anyone with the Editor role or higher in the project can open the **Pending** launch from **Launches** and continue it.

Every wizard control is in [Run manual tests with the Test Wizard](https://docs.qualflare.com/docs/runs/manual-testing).

## Finalize the launch

When every case has a verdict, the wizard shows "Run complete." Click **Finalize Launch**, and Qualflare opens **Launches**. Until you finalize, the launch stays **Pending**. A manual launch starts no AI launch analysis, failure clustering, Slack or webhook notification.

## File a defect for each failure

1. Under **Analysis**, click **Defects**, then **Create Defect**.
2. Enter a **Name** that says what broke, such as `Saved card payment fails with an expired card`, and a **Description** that names the launch number and the test case. Set **Severity** and the **Environment** you tested in, which you can't change later. Click **Create**.
3. To route it, pick a team in its **Team** column ([Route a defect to a team](https://docs.qualflare.com/docs/defects/manage-defects#route-a-defect-to-a-team)).

## Repeat the cycle next release

1. Keep the suite current. A plan holds the cases you saved: when you add a case to the suite, tick it on the plan's **Test Cases** tab and click **Save Cases**.
2. On **Test Plans**, click **Create Run** on the same plan. Each run is a new launch with the plan's cases.
3. Compare the cycles: on **Launches**, filter **Automation** to **Manual**; a case's **History** tab lists its runs ([Test cases](https://docs.qualflare.com/docs/test-management/test-cases)).

   *Figure: Each Create Run of the plan is one launch, so the release cycles line up on Launches with their pass rates.*

To link a cycle to a release [milestone](https://docs.qualflare.com/docs/test-management/milestones), start it from **Launches** > **Start Launch** instead: choose the suite, then set **Milestone**. **Create Run** has no milestone field, and each **Start Launch** creates a new test plan, which counts toward the workspace's plan limit.

## Verify

You should see one finalized launch per cycle on **Launches**, marked **Manual**, with the plan's cases and its pass rate, and each defect on **Defects** as **Active**.

## Troubleshoot

| Problem                                                             | Cause and fix                                                                                                                                                                           |
| ------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| The wizard shows `Select environment and language first`            | Choose **Environment** and **Language** at the top, then record the verdict.                                                                                                            |
| The run has fewer cases than the suite                              | Only the plan's **Test Cases** tab runs. Tick the missing cases there and click **Save Cases**.                                                                                         |
| **Create Test Plan** fails                                          | The workspace is at its test plan limit, and the plans that **Start Launch** created count too ([Plan limits](https://docs.qualflare.com/docs/test-management/test-plans#plan-limits)). |
| Your milestone isn't in the **Milestone** field of **Start Launch** | The field lists only the open milestones among the project's first 10 milestones by number, so a newer milestone may be missing from it.                                                |

## Next steps

* [Run manual tests with the Test Wizard](https://docs.qualflare.com/docs/runs/manual-testing): every wizard control, verdict and setting
* [Test plans](https://docs.qualflare.com/docs/test-management/test-plans): pick cases, attach queries and check the plan limit
* [Milestones](https://docs.qualflare.com/docs/test-management/milestones): track a release across its launches
* [Create, triage and close defects](https://docs.qualflare.com/docs/defects/manage-defects): triage, route and close what the cycle found
* [Upload automated results](https://docs.qualflare.com/docs/get-started): add CI results next to your manual runs
* [Find your way around Qualflare](https://docs.qualflare.com/docs/get-started/navigating-qualflare): the sidebars, the header and the side panel