Introduction

A test suite in QMetry is a collection of test cases organized to test a complete scenario, such as BVT, smoke, or regression tests. Test suites are part of specific cycles but can be copied to new cycles for future testing. They are executed with environmental or configuration details to provide context on the testing setup.

Open

Test Suites Module - UI

The Test Suite module UI in QMetry enables users 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.

Icons on Test Suite List View:

Open

Arrange Columns

Users can personalize their view through the Arrange Columns option, and these customizations are saved for future sessions.

Customization Options:

• Show More Columns: Add additional columns to the view by selecting the checkbox.

• Hide Columns: Remove columns from the view by deselecting the checkbox.

• Re-arrange: Change column order by dragging and dropping the fields.

• Resize Columns: Users can adjust the width of the columns.

Filter Test Suites

Users can filter test suites by summary, release, cycle, and platform. For more precise filtering, users can also add custom fields to the filter criteria.

• Basic Filters: Basic filters like summary, release, cycle, and platform are provided for easy filtering.

• Advanced Filters: For more precise filtering, users can also add custom fields to the filter criteria by clicking on the '+' sign.

• Clear Filter: Click the Clear Filters button above the module grid or in the left pane to reset the view to its default state.

• Reset Filters: Select the Reset Filters option to revert all advanced filter fields to their default settings, removing any custom selections.

• Clear Sorting: Click the Clear Sorting button above the module grid to remove any applied sorting preferences.

Managing Test Suite Folders

Users can organize test suites into folders for more efficient management. Each folder groups test suites with similar attributes, enabling bulk operations such as cut, paste, copy, edit, and delete.

Folders can be created directly under the root directory or as subfolders within existing folders. Test suites within a folder inherit the default attributes of that folder. The number of test assets, including both active and archived test suites, is displayed next to each folder name.

Adding a Test Suite Folder

The tree/folder panel is expandable, allowing users to widen the area for longer folder names. Users can also hover over a folder to view its full name.

• On the Test Suite tree, click on the New Folder button to add a new folder.

• Enter Folder Name and click Create.

• The new folder is reflected on the tree.

Editing a Test Suite Folder

Steps to edit a test suite folder:

1. Select the folder on tree and click on the Edit icon on the toolbar.

2. The folder detail screen opens in editable mode.

Deleting a Test Suite Folder

Steps to delete a test suite folder:

1. Select the folder on tree and click on the Delete icon on the toolbar.

2. On deleting a folder, all the sub folders and entities within the folder will be deleted.

Include/exclude Test Suites from Sub Folders at Parent Folder

Users can choose to include or exclude test assets from sub-folders in the parent folder view. By default, assets from sub-folders are shown. To hide them, open the Options drop-down and uncheck "Include Entities from Sub-Folder."

Test Suite Detail Page

To view the Test Suite detail page, click the test suite entity Key in the grid view, which will display detailed information in the current window. For easier comparison, users can also open the page in a new tab.

The main screen of the Test Suite module displays test suites within the Project based on the selected folder.

Organize Tabs

The detail page of QMetry assets features various tabs. Users can customize the tab order, and this arrangement is saved for each user.

Navigation

Once on the test suite details page, users can return to the main test suite screen by clicking on the breadcrumbs.

Tabs

• 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 shows and allows editing of relevant details.

• 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 users 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, follow these steps:

• Open the Test Suite module.

• Click on the New button on the toolbar.

• The pop-up shows two options on it: Create Test Suite and Create Folder.

The Create screen opens for the test suite.

Enter the following fields to add a test suite:

• Summary - Enter the name of the test suite.

• Owner - Assign test suite owner.

• Status - Select suitable status from the drop down.

• Associated Releases: While adding a test suite, select the release and cycle for which the test suite is being added. The list of releases appears according to the releases added on the project details page (Projects > Project / Release / Cycle).

• 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.

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

  • Image Upload: Users 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.

• Platforms: It is mandatory to link the platform for the execution of the test suite. Read more details in the section below.

• Link Test Cases: It is mandatory to link at least one test case to create a test suite. Read more details in the section below.

• 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 with Test Suite

Linking a platform is mandatory for executing a test suite. Users must associate platforms with test suites to conduct test runs. A default platform, “No Platform,” is provided for new test suites. Users can add additional platforms via Projects > Platforms.

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

2. Click on the Link button.

3. The Link Platforms pop-up opens with the list of Platforms on it. "No Platform" is available by default.

4. To manage a long list of platforms, users 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’.

6. Select single or multiple platforms from the list.

7. Click the "Link Selected Platforms" button.

View Linked Platforms

After creating the test suite, users can view all linked platforms from the Platform tab. This tab allows users to add, delete, and view both active and archived linked platforms.

Linking Test Cases with Test Suite

There are three ways to link test cases with 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

Link 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.

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 from requirement, follow these steps:

1. Click the Link Test Cases from Requirement button.

2. A pop-up shows only requirements with associated test cases.

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

4. Select requirements to be linked

5. Click the Link Selected Requirement button.

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

Link Test Cases 

Users can link test cases individually by clicking the Link button. They can filter test cases, select multiple test cases, and then link them to the test suite simultaneously.

Users can apply Basic or Advanced Filters to quickly find test cases. Additionally, they can 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: Identifies test cases not linked to any test suite for the selected release and cycle, highlighting uncovered test cases.

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

Users 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.

• Select Test Cases: Choose the test cases you want to link to the test suite. Filters will adjust according to the selected project, with additional filters for Labels and Folder paths available.

• 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.

• Finalize Linking: After selecting test cases, click the Link Selected Test Cases button.

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 keys. A maximum of 500 entities can be linked at once.

To link entity key, follow the below steps:

1. Click on the Link by Entity Key button.

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

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

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

View Linked Test Cases

Users can view linked test cases on the Test Cases Tab of the Test Suite Detail Page. From this tab, users can also link or unlink test cases, reorder them, and export all linked test cases.

• Link: Users 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: Users can unlink selected test cases from this screen.

• Export All Test Cases: Users can export all 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, users 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

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.

Required Permissions:

• Integration app must be enabled in the QTM subscription.

• Export permission for the Test Suite module is required. Role-based access control is managed under Customization > Roles.

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.

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.

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.

Adding Attachments

The tab allows users to add attachments to the test suite. Read more Managing Attachments.

Test Execution

On the Test Execution tab, records are shown by platform after associating a release, cycle, and platform with a test suite. The number of test execution records corresponds to the various combinations of platforms, releases, and cycles linked to the test suite.

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 to meet their needs:

• Show/Hide Columns: Choose which columns to display or hide.

• Arrange Columns: Reorder columns to fit your preferred layout.

• Resize Columns: Adjust column widths for better visibility.

• Sort Executions: Organize test suite executions by different columns to easily find related information.

The Test Execution view configured in the Test Suite > Test Execution tab will also apply to:

• Bulk Operations: For eSignature-enabled projects, during bulk approval processes for statuses like Approved, Request Changes, and Closed.

• Traceability Report: When tracing by test executions.

From the Test Execution Screen, users can Assign Testers or Bulk Execute Test Cases.

A. Assign Tester:

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

1. Click on the Assign Tester tab. The Select User drop-down will become available.

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

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

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

B. Bulk Execute

Users can perform bulk execution of test cases from this screen. The process for bulk execution is detailed below.

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 Execute 

This feature enables bulk assignment of Execution Status, Execution Type, and Assignee 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.

2. Open a test suite detail page and select the Test Execution tab on it. The screen displays associated test cases.

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

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

On this screen, users can:

• Assign an assignee to the test cases

• Assign an execution status to the test cases

• Assign an execution type to the test cases

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

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.

Copying Test Suites 

Users can copy test suites in three ways -

(A) Copy individual test suite

(B) Copy test suite folder

(C) Copy test suites in bulk through Bulk Operations

Copy Individual Test Suites

To copy individual test suites, follow these steps:

1. Go to the Test Suites module.

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

Copy Test Suite Options

The following is the screen to select a folder and other options to copy the test suite. You can either -

(A) Copy Existing Release & Cycle or

(B) Link New Release & Cycle

Copy Existing Release & Cycle

When copying a test suite, users can configure various options:

1. Select Folder: Choose the folder where the test suite will be copied.

2. Platforms: Check this box to include associated platforms. It is selected by default but can be deselected if platforms have changed and are no longer needed.

3. Release & Cycle: Check this box to include associated releases and cycles. This is selected by default but can be deselected if not needed.

4. Test Case Version: Select this option to sync test cases with their latest unarchived versions. Deselect to use the preserved version.

5. Reset to Not Run: Check this box to reset the test case execution status to "Not Run."

6. Reset Assignee: Check this box to reset the test case assignee.

7. Execution Status: Choose the execution status to filter the test cases you want to copy.

   • Copy Platform with Selected Execution Status: Check this box to copy only the platforms that have test cases with the selected execution status.

Link New Release & Cycle

The option to link new release and cycle is only provided for single test suite copy operation.

The additional options on the screen are described below.

• Release & Cycle: Users can link new release and cycle while copying the test suite along with existing releases and cycles of the source test suite. Users can select one release and cycle at a time.

• Status: Select the execution status.

• Select Existing Release - Cycle for Mapping: This option is enabled only when the Reset Assignee checkbox is unchecked, allowing the assignee and status to be copied from an existing Release/Cycle. If the user does not want to reset the Assignee or execution status to Not Run in the new test suite, they should select the existing release and cycle from which to copy these values.

The following matrix shows the impact of the option selected on the screen.

Copy Test Suite Folder

1. Go to the Test Suites module.

2. Right click on the test suite folder that you want to copy and select Bulk Copy.

3. Select entities to copy with the folder and click Next.

4. Select Destination Folder and click Copy.

Copy Test Suites in Bulk Through Bulk Operations

1. Go to Test Suites module.

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

3. The Bulk Operations pop-up opens. Select the Copy option and click Next.

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

5. The following is the screen to select an existing folder/create a new folder and other options to copy test suites. Then click Copy.

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 a test suite folder

1. Go to the Test Suites module.

2. Right click on the test suite folder to move and select Bulk Move.

3. Select the Source Folder and click Next.

4. Select the Destination Folder and click Move.

The folder is moved under the destination folder.

Move test suites in bulk through Bulk Operations

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.

Bulk Operations on Test Suites

Read about Bulk Operations on Test Suites

Import Test Suites

Read about Import Test Suites

Export Test Suites

Read about Export Test Suites