Test Cases Overview

Test Case is a set of testing procedures, necessary inputs, execution conditions, and expected results that define a single test that needs to be executed successfully to achieve a testing objective. In Qase, Test Cases are exactly that - you can define various parameters and expected outcomes of a particular testing scenario. Let's get into creating a new Test Case.

There are a couple of ways to create a new Test Case. First is a "quick create": hit the button "+ Create case" in a Suite where you want it to be added, give your new Test Case a title - and that's it; other case details can be added later:

The second method allows you to fill out your new Test Case in full detail. Start by hitting the "+ Case" button above the Suite structure of the repository:

You are prompted to configure your new Test Case and provide all the information that should be considered.

Test Case Properties

Test Case properties are divided into several sections:

  • Basic: here, 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 Automated, To Be Automated, or Not Automated

      NB: 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:

NB: There is also the possibility to modify the values of system fields (available on the Startup, Business, and Enterprise plans):

  • Conditions: in this section, you can specify what should have taken place before the Test Case can be performed (Pre-conditions) and what actions should be performed after the Test Case has been performed (Post-conditions).

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

  • Custom Fields: it is impossible to predict what kind of unique parameters or properties your Test Case will require, which is where Custom Fields can help you. You can create your own Custom Fields of various data types to store any additional information about your test cases that are not covered by default properties. If you do not yet have any Custom Fields created, you won't see this section in the Test Case configuration.

  • Attachments: upload images, screenshots, video snippets, or other documents to your Test Case to add clarity or provide extra context.

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

  • Parameters: you can configure your test case to be parametrized and to be performed during a test run in several iterations, depending on how many parameter values you define for it. You also have the option to add multiple parameters and you can have multiple values within each parameter that you create.

After you add such parametrized case to a test run, there will be several instances of it added to the run, each representing a specific param value:

  • Test Case Steps: this section defines which actions should be taken while running a test case and the expected results for each step. For example, if I want to test my software module that provides GPS for connectivity, I'll need to explain which action needs to be performed and what will be an expected result. There are two types of steps to pick from, Classic or Gherkin:

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

Nested Steps

This is a list of sub steps you need to perform within a step. This step has a parent + children relationship. It is a step within a step.

To use a nested step, click on the three-dots-menu of a step and then click on "Add child step."

If you have Steps that will apply to several Test Cases of a Project and will have matching properties everywhere across the board, you can save yourself lots of manual labor by creating Shared Steps. Once you have at least one Shared Step created in the “Shared Steps” view of your project, you will see a button "+ Add Shared Step" available when creating/editing a case:

When configuring a Case Step, you can customize it using the buttons beside the "Expected result" field:

  1. You can attach files from your existing files in Qase or from your computer.

  2. You can duplicate/clone a step.

  3. You can create a Shared Step.

  4. You can add a step.

  5. You can add a nested step.

  6. You can delete a step,

__________________________________________________________________

Test Case Actions

Once you have filled in all the information about your Test Case, you can either:

  • Send to review: in this case, a new Test Case Review request will be created, and a person responsible for reviews will then give their decision on a submitted Test Case.

  • Save your Test Case

  • Save and create another

  • Cancel: exit Test Case creation; your changes will not be saved.

Once the Test Case is saved, you will now see it appear in your Repository structure in relation to Test Suites and other Test Cases. Your Test Case will get an automatically assigned code, consisting of Project Code and a number (for example, "MR-5", where "MR" stands for project code and "5" tells me this is the fifth Test Case in this Project):

If you click a Test Case in Repository view, a Summary Bar will open up on the right side of the screen, where you will be able to see your Test Case properties, as well as Edit, Clone, or Delete it:

If you have deleted a Test Case, it will reside in Trash Bin located in the three-dots-menu:

From the Trash Bin, you can restore a previously deleted Test Case:

Filters

When in Repository view, you can apply Filters to find Test Cases with specific properties:

In an example below, there are two filters applied - Cases that are of Normal severity and that are not automated:

To look up a test case by name, you can use the search box - simply start typing the name of a test case, and you will be shown matching test cases:

Once you have multiple Test Cases, you can perform bulk edits. Check the boxes of several Test Cases to:

  • Edit multiple cases' properties:

  • Perform an Express Test Run of selected Test Cases:

  • Delete Test Cases in bulk; when attempting to delete multiple Cases, you have to type "CONFIRM" into the field in order to prevent accidental deletion:

NB: This behavior is determined by a setting in project settings and can be switched on/off:

Did this answer your question?