Announcement: Major Enhancements to the Test Case Module in QTM v8.22.0

With the QMetry 8.22.0 Cloud release scheduled for August 2, 2025, QMetry will roll out two major enhancements to the Test Case (TC) module.

Purpose of this Document

This document aims to inform existing QMetry users about the upcoming changes and help them prepare in advance for a seamless adoption of the new features.

Customers are encouraged to review the upcoming changes to ensure a smooth transition.

Upcoming Enhancements to Test Case Module

As part of this release, the following key enhancements will be introduced:

Test Cases Reusability Across Multiple Folders: A single test case can be associated with multiple folders within the same project. This will allow users to reference the same test case (identified by its unique key) across multiple folders, within the same hierarchy or across different hierarchies, without creating duplicates.
Folder-Level Test Case Sequencing: Users will be able to organize the order of test cases within each folder. The sequencing will be unique to each folder, allowing teams to structure test cases based on specific scenarios or execution flows.

Impact on Existing Workflows and Reports

Because of these upcoming enhancements to the Test Case module, there will be significant changes to how test cases are managed, organized, and reported. These updates will affect both the functional workflow within the Test Case module and custom reporting configurations in QMetry Insights.

Users can expect changes in folder behavior, test case visibility, and navigation. In addition, custom reports will require updates to remain compatible with the enhanced data structure.

Changes to Current Flow in Test Case Module

The “Project Root Folder” in the Test Case module will, by default, display all active test cases. Any newly created test case will be saved under the “Project Root Folder”, in addition to the selected folder. The “Include Entities from Sub Folder” option will no longer apply to the Project Root Folder; however, it will still apply to other folders.
All archived test cases will disassociate from their current folders. They will only be visible when the Show Only Archived Test Cases filter is applied and will be available under the Project Root Folder.

Notes
- This shall apply to both previously archived and newly archived test cases.
- For reference, the test case change log will retain the original folder path.
- Archived test cases will be excluded from folder-level counts.
- Archiving a test case will automatically disassociate it from all associated folders.
- While unarchiving, users will be able to move the test cases to one or more folders as needed.

This approach aims to ensure a clear distinction between active and archived test cases, enhancing usability.

Archiving a folder will only archive the folder and will not archive the test cases it contains. All test cases within the folder will be disassociated when the folder is archived. While archiving the folder, users will have the option to move these test cases to another folder. Users must archive test cases separately if they want to archive them.

This provides greater control and flexibility, allowing teams to manage folder structures without affecting active or reusable test cases.

Sorting by Test Case Folder Path will no longer be available across any screens in the application.
The total count of test cases will not be displayed next to the project root folder, as a test case can now exist in multiple folders.
The folder path navigation breadcrumbs at the top of the Test Case details screen will display the folder from which the test case is being accessed. This ensures accurate context when a test case is referenced across multiple folders. Sharing the link to the test case will open it from the Project Root Folder.

Changes to Custom Reporting (QMetry Insights)

Note

The changes to custom reporting will be rolled out on 2 August 2025 with QTM v8.22. Users are requested to perform the recommended actions only after the release.

Impact on Custom Gadgets

Custom gadgets created using Visual Reports that include the “Test Case Folder ID” or “Test Case Folder Path” fields or filters will display incorrect folder details.

Recommended Actions

Edit the gadget to remove these fields and filters.
Re-apply the fields and filters.
Review the report carefully for any inconsistencies after re-applying.

Impact on Custom SQL Gadgets

Custom SQL gadgets created using Advanced Query Reports that include the fields or filters “testcases.folderName”, “testcases.folderPath”, or “testcases.tcFolderID” will display incorrect data.

To resolve this, a new table, testcasefolder, will be introduced to correctly fetch or filter folder-related data.

Recommended Actions

Join the testcasefolder table with your existing query.

For example,

select tc.entityKey,tc.summary,
tcf.folderName,tcf.folderPath,tcf.testcaseFolderID from testcases tc join testcasefolder tcf
on tc.testcaseID = tcf.testcaseID where tc.projectID in (`@filter.project`);

Additional Enhancements in This Release

To support longer usernames, the maximum field length for Username and Alias will be increased to 256 characters.

If you have any questions or require help preparing for these updates, please don’t hesitate to contact QMetry Support.