Creating Test Cases
Create test cases manually, import them from BDD feature files, or leverage AI to auto-generate test cases. This flexibility helps teams build and manage test cases based on their preferred workflow.
Creating New Test Cases
The Create New Test Case screen lets you define test case details, link requirements, add test steps, associate a test suite and plan execution, all in one place.
To create a new test case, perform the following steps:
Go to the Test Cases module.
Click New.
Enter Test Case Details: Fill in all required fields under System Fields and User-Defined Fields (see field reference tables below).
Add test steps in the Test Steps section.
Link Requirements (Optional): Select from the list or enter the Requirement Entity Key directly. You can link up to 500 requirements.
Click Create to save the test case, or click Plan Executions to link it to a Test Suite and schedule execution before saving.
Note
Plan Executions is visible only for e-Signature disabled projects.
Link Test Case and Link Requirement permissions are required to link requirements.
System Fields
The System Fields section contains standard fields for test case definition:
Field Name | Description |
|---|---|
Summary | Name of the Test Case |
Priority | Minor, Major, Blocker, Critical, or Trivial. |
Labels | Choose one or more labels to classify the test case. |
Status | New, Approved, In Progress, Ready to Review. |
Owner | Assign an owner from users with access to the project. |
Test Case Category | Regression, Performance, Security, Functional, etc. |
Estimated Time | Specify the estimated execution time in HH:MM:SS format. Maximum: 99,999 minutes (1,666 hours). |
Description | Add a detailed description in plain or rich text. |
Folder Path | Auto-populated based on the creation location. Can be manually updated. |
User-Defined Fields (UDFs)
Configure UDFs for Test Case Module under Manage Fields.
Key Behavior
Custom fields added to the Test Case module appear under User Defined Fields.
You can configure UDFs as look-up lists, multi-lookup lists, or cascading fields.
For mandatory cascading fields, you must select both the parent and child values.
 |
Adding and Editing Test Steps
Test Steps define the actions and expected outcomes for test execution. To add or edit test steps, perform these steps:
Go to the Test Steps section.
Click the Expand icon for full-screen view.
To add a step:
Click the Edit icon or press TAB to navigate.
Click the Cog (⚙️) icon and select Insert Row for a new step.
Enter Step Description, Input Data, Expected Outcome , and any other UDF.
Repeat to add additional steps.
Reusing Steps
You can reuse steps from an existing test case or shareable test cases in two ways:
By using Insert Shareable Test Case option
By using Copy Steps from Existing Test Case options.
Access these options using the Cog (⚙) icon or the + icon on the Test Steps toolbar.
Insert Shareable Test Case
To insert a shareable test case, perform the following steps:
 |
Click the cog icon and select Insert Shareable Test Case.
In the Link Shareable Test Case screen, apply filter to locate the relevant test cases.
Click Save and Apply to save the applied filters. You ou can also filter the STCs by folder path.
Copy Steps from Existing Test Cases
 |
Click the Cog (⚙️) and select Copy Steps from Existing Test Case.
On the Copy Steps from an Existing Test Case screen, select the Project in the Project drop-down list.
Expand the test case containing the required test steps.
Select the test steps and click Copy or Copy and Close.
Select Copy if you want to select steps from different projects. You can select the steps, click Copy, change the project in the dropdown and continue selecting test steps.
Note
QMetry preserves the applied filters.
Enable Include Entities from Sub Folder to display STCs from the selected folder and all its sub-folders. Disable it to show STCs from the selected folder only.
Editing Steps
Hover over a step field and click the Edit icon to enable inline editing.
Press tab or click outside to save changes.
Note
Additional UDF columns appear beside default fields if added in Customizations.
Column arrangement changes in UDF step fields are reflected across all relevant screens: Execution, Detail, Version, and Exploratory Testing.
Entering Risk Analysis Fields
Note
This section is visible only if you have enabled Risk Analysis feature from General Settings under Projects.
Enter: Risk Type, Risk Category, Likelihood, Impact.
The system calculates Risk Priority Number and Extent of Testing, helping prioritize test cases.
Linking Requirements
Note
Get Link Test Case and Link Requirement permissions to link requirements.
To link requirements, perform the following steps:
Click Link.
You can link requirements by Entity Key or by selecting them directly from the Linking screen.
You can create a new requirement from the Linking screen and link it to the test case.
Note
You can link up to 500 requirements to a test case using the Link Requirements section.
Entering Test Case Details
System Fields
The System Fields section contains standard fields for test case definition:
Field Name | Description |
|---|---|
Summary | Name of the Test Case |
Priority | Assign a priority level: Minor, Major, Blocker, Critical, or Trivial. |
Labels | Choose one or more labels to classify the test case. |
Status | Select from: New, Approved, In Progress, Ready to Review. |
Owner | Assign an owner from users with access to the project. |
Test Case Category | Categorize as Regression, Performance, Security, Functional, etc. |
Estimated Time | Specify the estimated execution time in HH:MM:SS format. Maximum: 99,999 minutes (1,666 hours). |
Description | Add a detailed description in plain or rich text. |
Folder Path | Auto-populated based on the creation location. Can be manually updated. |
User-Defined Fields (UDFs)
Custom fields added to the Test Case module appear under User Defined Fields.
Users can configure UDFs as look-up lists, multi-lookup lists, or cascading fields.
For mandatory cascading fields, users must select both the parent and child values.
Administrators can configure UDFs under Customization in Manage Fields.
|
Planning and Executing New Test Cases
Plan Executions help streamline test execution. Add a new test case to an existing test suite or create a new test suite and schedule its execution.
Create Test Suite
Note
Requires Create Suite, Link Test Case, Link Test Suite permissions.
Click Create Test Suite to open the creation screen. Fill in the details below and click Proceed With Executions or Create Test Suite to save.
 |
To create a test suite, perform the following steps:
Enter test suite details.
Associate a Folder Path
Link one or more Releases, Cycles, and Platforms.
By default, Release and Cycle are auto-filled from the Test Case and owner defaults to the logged-in user.
You can select multiple values in the Release, Cycle and Platform. The Release and Cycle values are inherited from the Test Case.
Note
The entity key of the newly created Test Suite appears at the top. Click it to navigate to the Test Suite. All linked test cases are listed in the Test Cases section.
Link Existing Test Suite
Note
Requires Modify Suite, Link Test Cases and Link Test Suite permissions.
You can associate a test case with only one Test Suite.
The system excludes the following Test Suites from the list:
Test Suites without an associated Release, cycle or platform.
Test Suites in which all associated Releases, cycles or all platforms are archived.
Archived Test Suites.
Link Existing Test Suite opens the list of available Test Suites in the current project.
Select the Test Suite and choose one of the following options:
Link and Close: Links the test case to the selected Test Suite and closes the screen.
Proceed with Execution: Links the test case to the selected Test Suite and initiates execution runs. You are redirected to the Execution Flow screen to begin execution.
Cancel: The test case is saved but not linked to any Test Suite.
Proceed with Executions
The Execution Flow screen displays the Test Suite Key, Summary, and all execution runs for the test case. Edit the following details for each run:
Field | Description |
|---|---|
Build Name | Build Name The mandatory build settings (project level) are applied automatically. |
Attended Time (timer) | Edit manually. It does not auto-start with execution. |
Planned Date | Optional. Select a planned execution date. |
Comment | Optional |
Execution Attachment | Optional files |
Link or Add Bug | Link or create bugs |
Execution Type | Defaults to Manual |
Tester or Execution Assignee | Defaults to logged-in user |
Setup Time | Hidden by default |
Execution Status | Editable |
Note
The project-level timer restriction for Actual Attended Time does not apply on this screen.
You can add or link existing bugs directly from the test case execution screen .
Test Case execution view
Step execution view.
