Creating Test Suite
To create a test suite, perform the following steps:
Go to the Test Suite Module.
Click .
Enter Test Suite Details like System Fields, User Defined Fields, Link Platforms and Test Cases.
Click .

Entering Test Suite Details
System Fields
Table 17. System FieldsField Name
Desc
Summary
Enter the name of the test suite.
Status
Select appropriate status: New, Approved, Open, In Progress, Ready to Review, etc.
Owner
Assign an owner from users with access to the current project.
Associated Releases
Select a release from the releases added on the project details page.
Associated Cycles
Cycle is mandatory for execution. The cycle list is prompted for the selected release.
Description
Enter the description for the test suite. This can be added as either Plain Text or Rich Text.
Folder Path
Select a specific folder for storing the assets during creation. (Default is root folder)
User-Defined Fields
Add details to the user defined fields. Manage User-Defined fields from Customization.
Linking Platforms
Linking a platform is mandatory for test suite runs. By default, the systems assigsn "No Platform" to all new test suites. You can add platforms from the Platforms tab in Projects.
To link platform, perform the following steps:
Click Link.
Select one or more platforms from the list. Use Filters to manage long lists.
Click Create New Platform to create and link a new platform. Read more on Creating New Platforms.
Click Link Selected Platforms.
Linking Test Cases
Note
At least one test case should be linked to the test suite to complete the test suite creation.
View platforms linked to a test suite from Test Execution tab on the test suite detail page.
There are three ways to link test cases with a test suite. Linking can be done while adding or editing a test suite:
Link Test Cases from Requirement
Link Test Cases
Link by Entity Key
Note
View test cases in the custom order defined within the test case folders by disabling option.
Linking Test Cases from Requirement
Linking a requirement to a test suite automatically includes all test cases associated with that requirement.
Note
Link Test Cases From Requirement links the version of the test case that is associated with that requirement. If eSignature is On for the project, then only “Approved” versions associated with the requirement gets linked.
Example 9. Linking Test Cases from RequirementThe requirement titled "Health Parameters" is associated with the following test cases:
Sleep Tracking
Calories Tracking
Stress Tracking
Step Count
These test cases are associated with the test suite "Health Stats". Now, the test suite “Health Stats” is executed, and the respective execution statuses for the test cases are recorded. The entire flow enables you to view the traceability of the requirement “Health Parameters”.
Linking test cases from a requirement minimizes manual effort and saves time by automatically including all relevant test cases. This approach also reduces the risk of overlooking any test cases planned for the requirement.
To link test cases to a requirement, perform the following steps:
Click Link Test Cases from Requirement.
Select the requirements to link.
Click Link Selected Requirement.
Note
You can link Test cases from requirements in different projects.
Linking Test Cases
Link ad-hoc or additional test cases to a test suite that were not planned or associated with a Requirement. This is particularly useful for organizations that manage their test cases only in and do not use as a requirement repository.
To link test cases, perform the following steps:
Go to Test Cases on the Create Test Suite screen.
Click Link.
Apply Filters to locate test cases.

View test cases based on the following criteria:
Show Test Cases Linked to Releases and Cycles: Displays test cases associated with the release and cycle linked to the current test suite.
Show Test Cases Not Linked to Any Test Suite: Highlights test cases that are uncovered in a particular release and cycle. Check linkage for each test case is not feasible. Thus, this option helps trace the uncovered test cases.
Hide Test Cases Already Linked to This Test Suite: Lists all test cases that are not already linked to the current test suite, preventing duplicate links.
Linking Test Cases From Other Projects: Link test cases from multiple projects by switching projects from the drop-down. The screen displays test cases for the chosen project.
Select Test Cases: Select the test cases to link to the test suite.
Link Specific Versions: If a test case has multiple versions, expand it to view all versions. Select the specific version to link with the test suite.
Linking Across Projects: To link test cases from multiple projects, select one project at a time. Search and link test cases for the current project before switching to another project to avoid losing previous selections.
Example 10. ExampleUser A selects some records from Project 1 and moves to Project 2 without linking them. In this case, all the selection of Project 1 gets wiped off.
Finalize Linking: After selecting the test cases, click .
Test cases from other projects show Entity Keys of the corresponding project. To view the test case of another project, click on the Test Case Entity Key. It opens the test case detail page in the respective project and changes your current project.
Link Test Case by Entity Key
Link the latest version of a test case to a test suite using comma-separated test case entity keys or requirement entity keys
Note
A maximum of 500 entities can be linked at once.
Use Case: This feature is useful to link test case to a test suite without searching them individually. For example, users have list of test case keys to be linked to a test suite, they can use this option to link the test cases directly. This feature will save the users' time in searching test cases in different folders and link them.
Linking from Test Case
Test case entity keys will be ignored if the test case is not found, archived, or "Not Approved" (if eSignature is enabled).
If a test case key is listed multiple times, it will be linked only once.
The latest version of a test case will not replace an older version if the older version is already linked. Only unarchived versions will be linked.
Skip Duplicate Linkage:
On: The latest version will be ignored if an older version is already linked.
Off: The latest version will be linked regardless of existing versions.
Linking From Requirement
The entity key will be ignored if the relevant requirement key is not found or is archived.
If the same requirement key is mentioned multiple times, the test cases linked to that requirement will be linked only once.
Skip Duplicate
On: Test cases already linked to the test suite are ignored; only the remaining test cases are linked.
Off: All test cases (unarchived version) are linked, regardless of previous linkages.