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 provides a unified interface that streamlines the process of test case creation. Create test cases, manage requirement linking, associate test suite, plan execution, and link defects, all at the time of test case creation.
To create a new test case, perform the following steps:
Go to the Test Cases module.
Click New.
Enter Test Case Details: Fill all required fields.
Link Requirements (Optional): Link requirements to the test case by:
Selecting requirements from the list.
Entering the Requirement Entity Key.
After entering the test case details:
Click Create to save the test case.
Click Plan Executions to link the test case to a Test Suite and plan its execution.
Plan Executions:
Note
This section is visible only for e-Signature disabled projects.
Plan execution of the newly created test case by:
Creating a New Test Suite
Linking an Existing Test Suite
Link the new test case to a test suite or link and execute it directly.
Link Test Suite and Close
Links the test case to the selected Test Suite and closes the screen.
Execute
Opens the execution screen to run the newly created test case within the linked Test Suite.
The system saves the test case and redirects to the Test Case list view, with the new test case added at the end.
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.
 |
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.
Shareable or Copied Steps
Insert Shareable Test Case: Click the Cog (⚙️) icon, select shareable test case and link it.
Copy Steps from Existing Test Case: Click the Cog (⚙️) icon, select steps and click Copy or Copy and Close.
The + icon can also insert shareable or copied steps.
User-Defined Test Step Fields
Additional UDF columns appear beside default fields if added in Customizations.
Column arrangement changes are reflected across all relevant screens (Execution, Detail, Version, Exploratory Testing).
Editing Steps
Hover over a step field and click the Edit icon to enable inline editing.
Press tab or click outside to save changes.
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.
Planning and Executing New Test Cases
Planning Test Executions
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
Get Create Suite, Link Test Case, Link Test Suite permissions to create a new test suite.
On clicking Create Test Suite, the creation screen opens. The entity key of the newly created test suite is displayed at the top. Click the entity key to go to the test suite. All test cases linked to the Test Suite are listed in the Test Cases section.
 |
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.
Link Existing Test Suite
Link Existing Test Suite opens the list of available Test Suites in the current project.
Note
Get 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.
Select the test suites.
Select one of the following options:
Link and Close: Links the test case to the selected Test Suite and closes the screen. No execution runs are created.
Proceed with Execution: Links the test case to the selected Test Suite and initiates execution runs. You will be redirected to the Execution Flow screen to begin execution.
Cancel: The test case is saved but not linked to any Test Suite, and no executions are created.
Proceed with Executions
Proceed with Execution directs you to the test execution flow. This screen displays the following details:
Test Suite Key
Summary
List of all test case execution runs.
You can edit the following details for each execution:
Field | Description |
|---|---|
Build Name | Build Name The mandatory build settings (project level) are applied when executing the test cases. |
Attended Time (timer) | Attended Time can only be edited manually. It does not auto-start with execution. |
Planned Date | Select the date to set planned date. Optional |
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 following project-level timer restriction does not apply on this screen: “Enforce time tracking of 'Actual Attended Time' through the timer on the execution screen, preventing manual entry or modification of the recorded time.”
You can add or link existing bugs directly from the test case execution screen .
Test Case execution view
Step execution view.
