Skip to content
The docs are now organized by product area. Old links still work. Report a broken link

Tutorial: run a manual regression cycle

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.

Last updated

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

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.

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

    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.

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

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.

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

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

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

ProblemCause and fix
The wizard shows Select environment and language firstChoose Environment and Language at the top, then record the verdict.
The run has fewer cases than the suiteOnly the plan's Test Cases tab runs. Tick the missing cases there and click Save Cases.
Create Test Plan failsThe workspace is at its test plan limit, and the plans that Start Launch created count too (Plan limits).
Your milestone isn't in the Milestone field of Start LaunchThe 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