Overview
A Test Case in Qase 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 a test case
a) create a Quick case
Quickly create a test case by clicking the "+ Create quick test" row in a Suite and type out a title. 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:
Conditions
Test Case Steps
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
Muted case: checkbox marking tests as muted so their results will not affect the overall status of test runs where it can pass even if the muted test fails.
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:
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.
Conditions
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 don't require any preliminary configuration. This is a multi-select dropdown and is configured from your Workspace Settings.
Add clarity and additional context to your Test Case by uploading images, screenshots, video snippets, or other documents.
NB: There is a 128MB 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.
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.
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
Step Action: A specific operation or task carried out within the test case step, such as interacting with an application interface or system.
Data: Input parameters or information utilized during the execution of a test, the influences the behavior of the system under test.
This field can be disabled from the project's settings, under test case -> 'Dataset"
Expected Result: The anticipated outcome or behavior that is considered correct for the given test case step.
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.
Nested Steps
This is a list of sub-steps to be executed within a main step. This relationship forms a parent-child structure, where a step contains smaller steps within it.
To create a nested step, click on the three-dots menu of a step and select "Add child step."
Shared Steps
To save time on repetitive tasks for Steps common to multiple Test Cases in a Project, consider creating Shared Steps.
Once you have at least one Shared Step in the "Shared Steps" view of your project, you'll find a "+ Add Shared Step" button when creating or editing a case.
When configuring a Case Step, you can customize it using the buttons beside the "Expected result" field:
You can create a Shared step / or turn a Shared step into a Regular step.
You can duplicate/clone a step.
You can edit a Shared step.
You can add a nested step.
You can delete a step,
You can attach files from your existing files in Qase or your computer.
Quick edit from preview
All of the test case properties, including test case steps, description and preconditions can be edited directly from the preview.
Test Case Actions
Once you have filled in all the information about your Test Case, you can:
Send to review: in this case, a new Test Case Review request will be created, and a person responsible for reviews will then decide on a submitted Test Case.
Save your Test Case
Save and create another
Cancel: exit Test Case creation; your changes will not be saved.
Find your test case after saving:
After saving the Test Case, it will be visible in your Repository structure alongside Test Suites and other Test Cases.
The Test Case will receive an automatically assigned code, combining the Project Code with a number (e.g., "DEMO-9," where "DEMO" is the project code, and "9" indicates the ninth Test Case created in this Project).
You can search your test cases using the code. Make sure to prefix the project code to the id.
When you click on a Test Case in the Repository view, a sidebar with a summary will appear on the right side of the screen.
You can view the Test Case properties and access options to Edit, Clone, or Delete it.
Restoring deleted cases:
If you have deleted a Test Case, it will reside in the Trash Bin located in the three-dots-menu:
From the Trash Bin, you can restore a previously deleted Test case:
Filters
When in the Repository view, you can apply Filters to find Test Cases with specific properties:
In the example below, there are two filters applied - Cases that are of Normal severity and that are Manual:
Search
You can look up a test case by its title, id, suite or any of it's fields' text.
Use the search box - start typing the name of a test case, and all the matching test cases will be shown:
Bulk actions
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 to prevent accidental deletion.
NB: This behavior is determined by a setting in project settings and can be switched on/off:
NB: This behavior is determined by a setting in project settings and can be switched on/off:
