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

Create and edit test cases

Create a test case in a Qualflare suite, add steps and expected results, set its state, priority and tags, insert shared steps and edit it later.

Last updated

To create a test case in Qualflare, open a suite in Browse and click Create Case, then add its steps on the Steps tab; you need the Editor role or higher in the project.

Before you begin

Editor+ · project (requires the Editor role or higher in the project)
  • A suite to hold the case. To make one, see Create a suite.
  • Each case counts toward your workspace's test case limit, 200 test cases on Starter (Plans and limits).

Create a test case

The Create Case dialog saves only the Name. Qualflare ignores the Description, Priority and Test Type you enter there: every new case starts with no description, Low priority, the E2E test type and the Draft state. You can't change the test type later in the app. After you create the case, set its description and priority as shown in Set state, priority, description and tags.

Open the suite's Test Cases tab

Click Browse in the project sidebar, then click the name of the suite the case belongs in. To start a new suite, click Create Suite first. Open the suite's Test Cases tab.

Create Case on a suite's Test Cases tab adds a case to that suite.

Enter a name and create the case

Click Create Case and enter a Name of 3 to 200 characters, for example "User can log in with valid credentials". Case names must be unique within a suite; the same name can exist in another suite. Click Create.

The Create Case dialog. Only the name you type is saved today.

Add steps and expected results

Open the Steps tab

Open the case and go to its Steps tab.

Add a step

Click Create Step. In Add Step, enter the Step Instructions (3 to 500 characters) and pick a Type: Precondition, Action (the default), Expected Result, Verification, Navigation, API Request, Data Input or Cleanup. Click Create, and repeat for each step.

Pick one of eight step types. An expected result is a step of type Expected Result.

Write the expected result as a step

There is no separate expected-result field. Add a step of type Expected Result, for example "The dashboard opens and shows the user's name".

Nest a step under another

Open the parent step's ⋯ menu and choose Add child step.

Tips for clear steps:

  • Start each step with a verb, such as "Click", "Enter" or "Navigate", and keep to one action per step.
  • Make expected results specific, never just "it works".
  • Include the test data, for example "Enter email: test@example.com".

Set state, priority, description and tags

  • Open the ⋯ (More options) menu next to the case name, choose Priority, then Low, Medium, High or Critical.
  • Choose Edit in the same menu to add a Description of up to 1,024 characters. Longer text fails to save.
  • Next to Tags under the case name, click the tag box (Add tags... while it's empty) and pick up to 5 tags. Create tag opens your workspace's Tags page.
  • A case you create starts in the Draft state. Change it with ⋯ > State: Draft, Review, Active or Outdated.

The state doesn't control what runs: a Draft case can still be added to test plans and runs. It does feed the suite's coverage score, where Active and Review cases count more than Draft ones. See Case states.

Set a case's state from the More options menu next to its name.

Insert a shared step

Core and above (available on Core, Scale, Enterprise, Open Source)
  1. Open the test case and go to its Steps tab. The case needs at least one step of its own first.
  2. Click the arrow next to Create Step (it appears once the project has a shared step) and pick the shared step from the Insert Shared Step list. It shows only the project's first 10 shared steps by number, so a newer shared step may be missing from it.
  3. Qualflare adds it at the end of the case as one Shared row. Expand the row to see its steps.
  4. To position it, open the shared row's ⋯ menu and choose Move Up or Move Down.

Remove in the same menu takes the shared step out of this case only. It needs the Owner role. A case stores a reference to the shared step, not a copy. When you edit the shared step, the change shows up in every case that uses it.

Insert Shared Step appears once the project has a shared step and the case has a step of its own.

To create one, see Create a shared step.

Edit a test case

Open the case from Browse, a suite's Test Cases tab or Explore.

  • Name and description: open the ⋯ (More options) menu next to the case name and choose Edit. The Edit Case dialog has Name and Description. Click Save.
  • Priority, state and tags: use Priority or State in the same ⋯ menu; the change applies at once. Use the tag box next to Tags to add or remove tags (up to 5).
  • Steps: on the Steps tab, click Create Step to add a step. Open a step's ⋯ menu to Edit, Duplicate, Add child step, Move Up, Move Down or Delete it, or drag a step by its handle. Deleting a step needs the Owner role.
  • Steps on automated cases come from your test reports. You can't add, edit, move or delete them in the app, and the next upload replaces them.

Deleting test cases also deletes every suite in the project that has no cases left, including suites that were already empty. Archive cases you might need later instead of deleting them.

To remove a case, archive it, or delete it as described in Delete a case.

To change many cases, select them in Browse or in a suite's Test Cases tab to Archive or Delete them. To Unarchive, turn on the Archived filter first. In Explore, the bulk action that works is Delete. There is no bulk edit: change priority and state one case at a time. Changes to a shared step show up in every test case that uses it, so review them carefully.

Review a case's history

  • The History tab lists the case's past runs: launch, branch, milestone, environment, language and duration.
  • The Change log tab lists each change: action, actor, description, changes and date.
  • Qualflare doesn't keep earlier versions of a case, so there is no compare or restore.
The Change log records each change to a case. Qualflare keeps no earlier versions to restore.

Reuse test content

Qualflare has no case templates and no bulk clone. To reuse work:

  • Shared steps: put step sequences that many cases repeat, such as logging in, in a shared step. See Insert a shared step.
  • Clone a suite: in Browse, open the suite row's ⋯ menu and choose Clone. The copy is named <suite name> (Copy N), where N is the new suite's number. It holds a copy of each case's name, description, priority, state and test type. Steps, tags and attachments are not copied.
  • Quo: the Quo AI agent can create several cases in a suite from a short description.

Verify

You should see the new case in the suite's Test Cases tab with its number, the Draft state and Low priority. Its Steps tab lists each step with its type and a Manual badge.

Troubleshoot

  • A minimum of 3 characters is required.: the name or the step instructions are shorter than 3 characters.
  • Maximum 200 characters allowed.: names are 3 to 200 characters.
  • Maximum 500 characters allowed.: step instructions are 3 to 500 characters.
  • The Priority, Description or Test Type you set in Create Case are gone: the dialog saves only the name (see Create a test case).
  • Insert Shared Step is missing: the project has no shared step, the case has no step yet, or your plan has no shared steps.
  • A shared step is missing from Insert Shared Step: the list shows only the project's first 10 shared steps by number.
  • You can't edit a step: steps on automated cases come from your uploads.
  • Clone fails: cloning currently fails for cases created in the app or from uploaded results.