Test cases

What is a test case in software testing?

A test case contains all the details about our test. In Qase, a test case is a specific set of instructions and conditions that outline a test to be carried out successfully. It includes testing procedures, necessary inputs, execution conditions, and expected results to achieve a testing objective.

In Qase, you can define various parameters and expected outcomes of a particular testing scenario.

Create Test Case

A. Create a quick test case

Quickly create a test case by clicking the "+ Create case" button in a Suite, by providing a title, and add other details later if needed.

B. Create a detailed case

The second method lets you fully detail your new Test Case. Click the "+ Case" button above the Suite structure in the repository to begin.

You'll be guided in setting up your new Test Case and providing all the necessary information.

Test Case Properties

Test Case properties can be divided into several sections:

Basic fields

You will define the following Test Case properties:

  • Title: define the name of a test case

  • Status: can be either Active, Draft, or Deprecated

  • Description: additional details for more context about a test case

  • Suite: choose here which Test Suite your new case belongs to

  • Severity: can be either Trivial, Minor, Normal, Major, Critical, Blocker, or Not Set

  • Priority: can be either Low, Medium, High, or Not Set

  • Type: select what type of testing is applicable for your test case

  • Layer: pick a layer of the test case, whether it's an end-to-end, API, or a unit test

  • Is flaky: if a test case is unstable, you can mark it as flaky

  • Milestone: select whether a test case is related to one of your Milestones, which you can create separately

  • Behavior: can be either Destructive, Negative, Positive, or Not Set

  • Automation Status: you can choose from Manual or Automated

  • To be automated: a checkbox property only available for those cases that have a "Manual" automation status


Here, you can outline what needs to happen before conducting the Test Case (Pre-conditions) and the actions to be taken after the Test Case is completed (Post-conditions).


Tags are a quick way to label your test cases with values that doesn't require any preliminary configuration.

Custom Fields:

Predicting the specific parameters or properties needed for your Test Case is challenging, and this is where Custom Fields come in handy.

You can make your own Custom Fields with different data types to store extra information about your test cases not included in default properties. You won't find this field If you haven't created any Custom Fields yet.

Add clarity and additional context to your Test Case by uploading images, screenshots, video snippets, or other documents.

Note: There is a 32MB maximum size for a single file that can be attached.

You can set up your test case to be parametrized and run it through multiple iterations during a test run, depending on the parameter values you define.

You have the flexibility to add multiple parameters, each with multiple values.

Once you include a parametrized case in a test run, multiple instances of it will be added to the run, each representing a specific parameter value.

Modifying fields

System fields can be optionally switched on and off via the fields section. Click the "Configure fields" button and select the field you want to configure. Click on the “Enable for all projects button” and then configure:

Note: The values of system fields can be modified. ​ (available on the Startup, Business, and Enterprise plans):

Test Case Steps:

This section outlines the actions to be taken and the expected results for each step when executing a test case. For instance, when testing a software module offering GPS connectivity, you must specify the actions to perform and the anticipated outcomes.

There are two types of steps to pick from -

a) Classic

b) Gherkin

Test Case can consist of several steps that must be performed; for every new step, hit the "+ Add Step" button on the bottom.

Last updated