Introduction

A Test Suite in QMetry is a collection of test cases organized in a specific order to test a complete end-to-end test case scenario. A test suite may also be created to test a complete set of test cases by type like a BVT, smoke test, regression, etc. In QMetry, test suites are part of specific cycles but can be copied to new cycles for future testing.

This allows QA groups to plan out testing for a specific development cycle. Test Suites are executed against a platform that provides any needed environmental or configuration information. This is to help QA understand not just what functions were tested, but against what hardware and/or software it was tested.

Key Features of the Test Suite Module

The Test Suite module UI in QMetry enables you to:

• Create and organize test suites for efficient test management.

• Define and manage test case execution plans within each test suite.

• Monitor the status and results of test cases and suites.

• Configure test suite settings and parameters to tailor them to specific testing needs.

Test Suites Module - UI

The Test Suite List View screen enables you to check the following:

• Total Test Case Executions and Total Unassigned Executions for each test suite.

• Linked Platform and Linked Test Cases Count.

• Total Estimated Time and Remaining Execution Time.

• Review details such as Created By, Updated By, and their corresponding dates.

This allows the QA Manager to see Total Test Case Executions and Total Unassigned Test Case Executions on the Test Suite screen, and filter test suites by these fields for tracking and management.

The Test Suite list view screen allows users to perform the following operations:

1. Sorting and Clear Sorting

Sorting

Clear Sorting

2. Set Filters

You can filter test assets by any system or custom fields on all module grids.

3. Manage Grid Columns

The Arrange Columns option in the Test Suite Module grid enables you to customize the asset view. Refer to the Manage Grid Columns page to know more.

Icons on Test Suite List View

The table below provides a brief description of the icons in the test suite list view:

Folder Management

Organize your requirements in a hierarchical structure using folders. To learn more about available actions, refer to Basic Folder Operations document.

Bulk Operations

Perform bulk copy or move actions at the folder level within or across projects. To learn more, refer to the Bulk Copy/Move document.

Test Suite Detail Page - UI

To view the Test Suite detail page, click the Test Suite Key in the grid view. To open it in a new tab or window, right-click the entity key.

Tabbed View Vs Combined View

Individual Section Tabs

The Test Suites detail page includes tabs for Test Executions, Test Cases, Platforms, Details, Release & Cycles, Attachments, Comments, and Change Log. Each tab displays relevant details. The details are editable.

Test Execution Tab

The test execution tab enables you to execute test runs, schedule test executions, archive test runs, assign tests, share test executions with the team, bulk execute test executions, and assign planned dates to the test suites.

For further information, refer to the Test Execution Section in this document.

Test Case Tab

The Test Cases tab on the Test Suite Detail page provides a comprehensive view of linked test cases, displaying key details such as testing type, testing category, status, priority, and the test case folder path for easy traceability.

You can manage test cases from this tab by linking or unlinking them, reordering as needed, and exporting all linked test cases.

Linking Test Cases 

You can link test cases individually by clicking the Link button or choose to link test cases in bulk. You can filter test cases, select multiple test cases, and link them to the test suite simultaneously. You can also filter test cases by folder path to link test cases grouped under a particular folder.

• Link: You can link individual test cases or all test cases associated with a requirement using the following options:

  • Test Case

  • Test Case from Requirement

  • By Entity Key From Requirement

  • By Entity Key From Test Case

• Unlink Selected: You can also unlink selected test cases from this screen by selecting the test cases and clicking on Unlink Selected.

• Export Selected Test Cases: You can export selected test cases linked with a test suite using this button.

• Change Order: Test cases linked to the test suite will appear in the same order on the test execution screen. However, you can adjust this sequence to match the desired execution flow. Use the Cog icon and select one of the following options:

  • Move Up

  • Move Down

  • Shift to First

  • Shift to Bottom

Details Tab

The Details tab lets you edit and update the status, owner, description, and execution command of the test suite.

Release & Cycle tab

The release and cycle tab lets you view the associated releases and cycles to the test suite. You can edit, update, unassociate, or add a new release and cycle from this tab.

Platforms Tab

The Platform tab within a test suite displays all associated platforms. From this tab, you can also link new platforms, unlink existing ones, and view both active and archived linked platforms.

Attachment Tab

The Attachments tab lists all associated files, allowing you to add new attachments, download files, or delete selected attachments from this section. Read more Managing Attachments.

Combined View

The tab shows the previous view of the details page. All sections are visible on a single page, but the information is read-only and cannot be edited.

Managing Test Suites

Managing test suites in QMetry allows you to efficiently add, organize, filter, and view detailed information for test suites within a project, streamlining test management and comparison.

Adding a Test Suite

To add a test suite, perform the following steps:

1. Open the Test Suite module.

2. Click on the New button on the toolbar.

On the Create screen, enter the new test suite details.

System Fields

Enter the following fields to add a test suite:

All About Rich Text Editor

• Rich Text: The Rich Text Editor allows you to format text, insert images, hyperlinks, and tables, reducing the chances of missing important details.

• Image Upload: You can add images up to 1 MB to any Large Rich Text Editor field (System or Custom) by:

  • Browsing and uploading the image,

  • Inserting the image via URL,

  • Copying and pasting the image directly into the editor.

• User Defined Fields: If UDFs are added for the test case module, then they are displayed on the Create Test Suite screen and Test Suite Details screen.

Automation Testing

For Automation Testing, refer to QMetry Automation Agent.

Linking Platforms

Linking a platform is mandatory for executing a test suite. You must associate platforms with test suites to conduct test runs. A default platform, “No Platform,” is provided for new test suites. You can add platforms from the Platforms tab under Projects.

1. Go to the Platforms section on the Test Suite creation page.

2. Click on the Link button.

3. Select a platform from the list. "No Platform" is available by default.

4. To manage a long list of platforms, you can filter by Platform Name, Creation Date, or Created By.

5. Users can also create a new platform from this screen by clicking on the Create New Platform. It opens the Platforms screen in a separate tab, wherein you can add new Platforms. Read Creating New Platforms. Once you are done adding platforms, reload the Link Platforms screen.

6. Select one or more platforms from the list.

7. Click Link Selected Platforms.

The selected platforms are now linked to the test suite. Navigate to the Test Execution tab on the test suite detail page to view the test suite with the newly linked platforms. If a test suite is saved without linking a platform, a confirmation message is displayed.

Linking Test Cases

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

Linking Test Cases from Requirement

Linking a requirement to a test suite automatically includes all test cases associated with that requirement, eliminating the need for individual selection. This method ensures comprehensive requirement coverage and traceability, enabling the QA team to monitor requirements from creation through execution.

Additionally, test cases from requirements in different projects can also be linked.

Example

The 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:

1. Click Link Test Cases from Requirement.

2. You can filter requirements based on Summary, Version ID, Priority, Labels, Releases, Cycles, Created By, or Folder Path.

3. Select the requirements to link.

4. Click Link Selected Requirement.

Test cases linked to the selected requirements will be added to the test suite.

Linking Test Cases 

You can link test cases individually by clicking the Link button or choose to link test cases in bulk. You can filter test cases, select multiple test cases, and link them to the test suite simultaneously.

Use Case: Link Test Cases enables you to link ad-hoc or additional test cases to a test suite that were not planned or associated with a Requirement. Organizations that manage their test cases only in QMetry and do not use QMetry as a requirement repository should use the Link option to link test cases to test suites.

To link test cases, perform the following steps:  

1. Go to the Test Cases section on the Create Test Suite screen.

2. To view the list of test cases that are available to link, click on the Link button.

3. The Link Test Cases screen opens.

You can apply Basic or Advanced Filters to quickly locate test cases. (Refer to the filters section above for detailed instructions on using filters.)

Additionally, test cases can be viewed 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: Identifies all the test cases that are not linked to any test suite for the selected release and cycle, highlighting uncovered test cases. To apply the filter, first select Release and Cycle under Basic Filters.

• Hide Test Cases Already Linked to This Test Suite: Hides test cases already linked to the test suite to avoid duplicate linkage.

• Linking Test Cases From Other Projects: You can link test cases from different projects by selecting the project from the Project drop-down. The screen will then display test cases for the chosen project.

• Finalize Linking: After selecting test cases, click the Link Selected Test Cases button. The test case(s) are linked to the test suite.

If test cases from another project are linked, then the test cases show the Entity Key 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 

Users can link the latest version of a test case to a test suite using comma-separated test case entity keys. Link Test Cases From Requirement automatically links test cases versions associated to that requirement. If eSignature is On then only “Approved” versions associated to the requirement will be linked.

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.

Steps:

1. Go to the Test Cases tab of the test suite page.

2. Click on the Link by Entity Key button.

3. Two options will appear - From Requirement and From Test Case.

4. Select either of the options and a pop-up appears.

5. Enter Requirement entity keys or Test case entity keys.

6. Click on Link.

Importing Test Suites

The Import option allows you to import test suites from Excel and Jira.

Editing a Test Suite

An in-place editor is available on detail screens for all test suites. Hover over a field and click the edit icon to open it in editable mode. Users can then enter a new value and save the changes. To modify a value on the test suite details page, simply hover over the field and click the edit icon.

To edit a test suite, perform the following steps:

1. Navigate to the test suite details screen.

2. Access the Details tab.

3. Hover over the values you wish to edit.

4. Enter the new values and click the checkmark to save your changes.

Editing Associate Releases & Cycles

Releases and cycles are initially associated with a test suite during its creation. To update these associations, users can do so via the test suite details page or the edit page.

To associate additional releases and cycles with an existing test suite:

1. Click the Add New button to enable the drop-down menus for selecting releases and cycles.

2. Choose the desired releases and cycles from the drop-down lists.

3. Click Save to apply the new associations. The updated releases and cycles will be displayed in the grid.

To remove an association, click Unassociate for the release and cycle combination you wish to remove.

View Archived Release & Cycles

Users can apply filters to view the required releases and cycles. To view archived releases and cycles, select the Show Archived checkbox in the filter options.

Copying Test Suites 

You can copy individual test suites as well as test suites in bulk by linking existing or new release, cycle and platforms. Read more about copy test suite.

Moving Test Suites 

Users can move test suites in three ways -

• Move individual test suite

• Move test suite folder

• Move test suites in bulk through Bulk Operations

Move individual test suites

1. Go to the Test Suites module.

2. Click on the Cog icon for the test suite that you want to move and select Move.

3. Select the Destination folder in which you want to move the test suite and click Move.

Move test suites in bulk

1. Go to the Test Suites module.

2. Click on the Cog icon on the header at the top right and select Bulk Operations.

3. The Bulk Operations pop-up opens.

4. Select the Move option and click Next.

5. Select test suites to be copied and click Next.

6. Select the destination folder to move the selected test suites. You can also create a new folder to move the test suites. Click Move.

Deleting a Test Suite

Users need to archive test suites before deleting them. The Delete option will be enabled only for archived test suites.

Archive Test Suites

User can archive test suites through any of the following ways:

• Clicking on the Archive icon at the top right corner on the test suite details page.

• Clicking on the Archive option on Cog icon of individual the test suite on the grid.

• To archive multiple test suites at once, select Bulk Operations > Archive Records. The screen only displays archived test suites.

• To view archived test suites on the grid pane, open the filter panel by clicking on the Filter icon. 

• Select the Show Archived Items check box.

• The grid pane at right starts displaying the archived test suites.

User can delete test suites through any of the following ways:

• Clicking on the Delete icon at the top right corner on the test suite details page.

• Clicking on the Delete button on the Edit screen of the test suite.

To delete multiple test suites at once, select Bulk Operations > Delete Records. The screen only displays archived test suites.

Sharing Test Suites with Other Users

Share Test Suites

Users can share a test suite with others via email. The recipient receives an email with the test suite summary, the message provided, and a link to the specific test suite for easy access.

Steps:

1. Open the test suite details page.

2. Click the Share icon at the top. The Share pop-up will appear.

3. Enter the email addresses of the users to whom the test suite should be shared. Multiple email addresses can be added.

4. Enter the message to be included in the email.

5. Click the Share button.

Copy Test Suite Link

Users can copy the test suite link and share it with other users to provide direct access to a specific issue. Authorized members can access the test suite directly via the shared link.

→ The following is the syntax of the URL:

https://<URL>>/#/<AssetType>/<AssetKey>

For example,

https://qtmtest.qmetry.com/#/test-suites/FIT-TS-9

Steps

1. Open the test suite details page.

2. Locate and click on the Copy Link icon on the breadcrumb navigation.

3. Users can share this link via any preferred communication channel.

Export Test Cases Linked to Test Suite

Users can export test cases linked to a test suite, allowing QA Managers to review selected fields in a PDF or Word format.

Options:

• Export all test cases

• Export selected test cases

Steps:

1. Navigate to Test Suite > Test Cases tab.

2. To export all test cases, click the Export All Test Cases button at the top of the test case list.

3. To export desired test cases, select the test cases to export and click on the Export Selected Test Case button.

4. Select the format PDF or Word to export the test cases.

5. Select the page orientation: Portrait or Landscape.

6. Open the Test Case Fields drop-down, and open the Test Cases/Test Steps tab.

7. Select the fields you want to export the details of the required fields of the test cases and test steps.

8. Click Save.

9. Select from the Additional Options:

• Test Suite Details

• Test Case Approval Details (This option is available only for the eSingature-enabled projects.)

• Issues Linked to Test Cases

• Requirements Linked to Test Case

10. Click on the Export button.

Users can view the progress in the Scheduled Task section.

Anchor

Anchor

​Test Execution

Platform-wise records appear on the Test Execution tab once you associate Release, Cycle, and Platform to a test suite. Test Execution records are added on the screen in accordance with the number of platforms, releases, and cycles linked to the test suite.

For example, if there are 2 Releases, 4 Cycles, and 2 Platforms associated with the test execution, then the number of test execution records will be 16 for each combination of Release - Cycle - Platform.

The screen displays details like Test Suite Summary, Release, Cycle, Platform, Status, and Execution Time.

Customize the Test Execution Tab View

Users can adjust the Test Execution tab view in the test suite through the arrange column option on the screen.

• Show/Hide Columns: Select or deselect checkboxes to display or hide specific fields accordingly.

• Reorder: Reorder columns to fit preferred layout by dragging and dropping the fields.

• Resize Columns: Adjust column widths for better visibility by dragging the borders.

Users can also filter and sort test suite executions by different fields to easily find related information.

Test Execution Tab Fields

• Execution Type

• Status

• Total Test Case Executions and Total Unassigned Test Case Executions

Assign Tester

To assign a tester to execute a test suite on a specific platform:

1. Select the test suite(s) by checking the corresponding boxes.

2. Click on the Assign Tester button.

3. Choose a user from the drop-down menu.

The selected tester will be assigned to execute the chosen test suite on the designated platform.

Planned Date of Execution

You can manually record the planned execution date for each test case run using the "Planned Date” field. This feature enables testers to schedule and document intended execution dates, improving visibility, tracking, and reporting for planned versus actual timelines while ensuring alignment with project schedules.

Steps

1. Navigate to the test execution tab on the test suite module.

2. Select the desired test execution runs. To perform a bulk update, select multiple test execution runs.

3. Click on the planned date field and select the desired date.

4. If execution is not planned, then select "Set as Unplanned" option.

Planned dates can be bulk updated from the Execution Screen, the Test Executions tab, and the Bulk Execute section on the Test Execution tab.

Bulk Execute

This feature enables bulk assignment of Execution Status, Execution Type, Assignee and Planned Date for test suites with multiple test cases, platforms, releases, and cycles. Once triggered, the assignments are processed in the background.

Steps

1. Go to the Test Suite module > Test Execution Tab

2. Select the test cases you want to execute and click on the Bulk Execute button.

3. The next screen displays the combination of test cases with their associated Platforms, Releases, and Cycles.

On this screen, users can perform bulk updates for selected test cases, including:

• Execution Status

• Execution Type

• Assignee

• Planned Date

The image below denotes the selection range of respective checkboxes on the screen.

Bulk assign test cases to testers

• Select test cases/releases & cycles/ platforms to which you want to allocate an assignee.

• Click on the Assignee and select the user that you want to assign to the selected test cases and their platforms at a time.

Bulk Execute test cases

• Select test cases and platforms the execution status to update.

• Click on the Execution Status and select the status to apply to test cases and their platforms at a time.

Bulk set execution type

• Select test cases and platforms the execution type to update.

• Click on the Execution Type and select the type (Manual/Automated) to apply to test cases and their platforms at a time.

Bulk Set Planned Date

You can set a single planned date for multiple test cases in bulk.

Steps:

1. Select the test cases from the grid.

2. Open the Planned Date calendar and choose the desired date for the selected test cases.

3. If no planned date is available, click on Set as Unplanned.

The planned date for all the selected test cases will be updated in bulk.

Archive Test Execution/Test Run

The Test Execution Archive feature allows users to lock executions to prevent any further changes.

Test executions can be archived in the following scenarios:

• When the entire Test Suite is archived.

• When the associated Release or Cycle is archived.

• When the associated Platform is archived.

• When the Test Execution itself is archived.

• When the Project is archived.

Archived test executions will not appear on the Test Executions tab of the test suite.

Archive Test Runs Manually

1. Open the test suite detail page and go to the Test Execution tab. Click on the Archive button for the test run to archive.

The confirmation message pops up. Click Yes to proceed.

View Archived Test Runs

To view archived test runs, select the Show Archived Records check box in the filter on the Test Execution tab. This will display test runs archived due to platforms, releases, cycles, or the test run itself.

For imported data, any changes in the status of archived test case executions will be ignored.

Impact of Archiving a Test Execution/Test Run

• Any new test case linked to the test suite will not be added to the archived execution.

• Existing linked test cases would not be allowed to unlink if they are linked to an archived execution.

• When new version of test case is created ,it cannot be force-synced or manually sycned in the archived execution.

• In case of test case steps update in the existing version, any change in test case step data in that test case version will reflect in test cases under archived execution.

• Bugs, attachments which are part of archived executions cannot be unlinked.

• Test Case and Step Comments, Execution Status, Actual, Expected outcome added during execution cannot be changed for archived executions.

• When "archived" execution is unarchived, any test cases that are linked to the test suite, are auto-linked with the execution after unarchive.

• If an execution's release, cycle or platform are archived, it will not be allowed to unarchive.

• Deleting any executed test case or test case version will remove the executions from the archived executions.

• In a cloned project (with data), the archived test run also get copied.

• For eSignature enabled project, State (In-Review/Approve/Closed) of the test Run will not be allowed to change.

• Closed test execution can be archived but on unarchive test execution nothing will happen.

• Test case data grid related modification will not be reflected in archived execution.

Unarchived Test Runs/Test Executions

• Missing test cases will be linked on unarchive test execution with associated test case version and latest data grid values.

• Existing linked Test case version will not get modified on unarchive test execution.

• Manually archived test execution will not get unarchived if any associated archived Platform/Release/Cycle is unarchived.

• If Test Case-Test suite Data Grid Mapping is modified after archive test execution, then older mapping (steps) will be removed on unarchive test execution.

• In case of parameterized test case, edited value of test case will not affect test cases under the archived test run. Once the test run is unarchived, the values will be updated in the respective test cases.

Bulk Operations on Test Suites

Read about Bulk Operations

Import Test Suites

Read about Importing Test Suites (Executions) from Excel File

Export Test Suites

Read about Exporting Test Suites