Test Suites Module

Test Suites Module

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.

image-20240808-081102.png

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

The Test Suite module UI provides options to sort by name, date (newest or oldest first), hide empty folders, and include entities from subfolders, enhancing organization and ease of access to test suites.

Sorting

image-20240918-123858.png

 

Clear Sorting

 

image-20240918-123958.png
  1. Set Filters

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

Basic Filters

 

image-20240918-130122.png

Advanced Filters

 

image-20240918-130613.png
  • Basic Filters: Basic filters like summary, release, cycle, and platform are provided for easy filtering.

  • Advanced Filters: Users can add custom fields to the filter criteria for more precise filtering by clicking on the + sign.

To apply advanced filters, these are the steps:

  1. Click on the + button.

  2. Select the required filters.

  3. Apply filter values.

  4. Click Save and Apply.

For example, you want to filter test assets on Priority, and Entity Key. Click on the “+” icon and select the fields on the drop-down list. You can apply an advanced filter on Entity Key to search for test cases using comma-separated entity IDs, without specifying the complete Entity Key, as shown below.

image-20240918-130811.png

Filtered views are automatically saved for future use, eliminating the need to reapply the same filters repeatedly.

  1. Reset Filters and Clear Filter Value 

The Clear Filter Values option resets the values in the filter fields, allowing you to adjust criteria without recreating the filter. The Reset Filters option returns all filter settings to their default state, removing any selected fields.

Reset Filters

 

image-20240918-131102.png

Clear Filter Values

 

image-20240918-131141.png
  1. 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

image-20240808-083305.png

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

Column Icon

Column Name

Column Icon

Column Name

Linked Platform(s) Count

Linked Test Case(s) Count

Total Test Case Executions

Total Unassigned Test Case Executions

Total Remaining Execution Time (mins)

Total Execution Time (mins)

Managing Test Suite Folders

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

The default attributes set for a folder apply to all the test suites within that folder. You can also add test suites under the root folder. The count of test assets in a folder and the total test assets in the folder hierarchy are displayed alongside the folder name. The count includes active and archived test suites.

For example, this is the folder hierarchy: Folder A → Folder B → Folder C

If Folder A has 5 test suites, Folder B has 3 test suites, and Folder C has 2 test suites, the count will be displayed as follows.

Folder A (10) <------ Parent Folder

Folder B (5) <------Child Folder

Folder C (2) <------Subfolder of Child Folder

The Test Suite Module’s main screen displays test suites in the Project according to folder selection. To find the required test suites, you can filter on multiple columns.

Note

  • Make sure you have the necessary permissions for the operation by checking Roles under Administration for individual roles.

image-20240808-091537.png

Include/Exclude Test Suites from Sub-folder at Parent Folder

You can 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.

Learn about the available actions for folders in Basic Folder Operations.

Refer to Bulk Copy/Move at the directory level within/across the project.

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.

image-20240808-093812.png

Navigation

QMetry enables seamless navigation within the test suite module. You can move between test assets using Breadcrumb navigation or the Previous and Next buttons. Refer to the QMetry User Navigation page for details.

Organize Tabs

The detail page of QMetry assets features various tabs. You can customize the tab order with the drag-and-drop feature, and this arrangement is saved for each user.

For example, the tab order of the Test Suites module is changed by user "A" for the project "PRO1". Now "A" is switching to another project, "PRO2". The tabs can be seen in the same order as in the project "PRO1".

image-20240918-133954.png

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.

image-20240919-082033.png

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.

image-20250409-081740.png

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

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

Unlinking test cases after execution will also remove all associated executions from the test suite for all releases, cycles, and platforms.

image-20250409-081927.png
  • 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.

image-20240919-083117.png

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.

image-20240919-083520.png

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.

To view archived platforms, use the Show Archived filter available in the Filters pane.

image-20240808-114833.png

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.

image-20240919-063124.png

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:

  • Open the Test Suite module.

  • Click on the New button on the toolbar.

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

image-20250409-082811.png

System Fields

Enter the following fields to add a test suite:

Field Name

Description

Field Name

Description

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)

All About Rich Text Editor

Note

  • To use rich text, enable the Enable Rich Text parameter for the Project from Projects under Project Management.

  • Refer to Enable Rich Text Editor for more details.

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

Notes

  • Multiple images can be copied and pasted simultaneously. Images can be previewed by clicking on them.

Notes

  • The supported file formats to upload/copy-paste the image are JPG, JPEG, PNG, and GIF.

  • The maximum file size should be 1 MB (for images uploaded through browsing).

  • Users can paste the HTML/XML content into the Source editor of the "Large Text" field type, and it auto-renders the code to show the text outputs on the screen.

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

image-20240917-110843.png
  1. Select a platform from the list. "No Platform" is available by default.

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

image-20240807-115944.png
  1. 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.

  2. Select one or more platforms from the list.

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

Note

  • At least one test case should be linked to the test suite to complete the test suite creation.

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

image-20240917-111000.png

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

image-20240808-115645.png

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.

image-20240919-070625.png

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.

image-20240919-065651.png

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.

→ Use Case: There are more than thousand test cases in a cycle, QA Manager wants to find out test cases that are not linked to any test suite in a particular release and cycle. Checking each test case linkage is not feasible, hence, the manager wants a quick way to trace such test cases.

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

→ Use Case: When test cases are large in numbers, it is very inconvenient to remember which test cases are already linked to the test suite. Hence, testers need a way to hide already linked test cases.

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

→ Select Test Cases: Choose the test cases to link to the test suite. Filters will populate 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.

For example, User A is in Project 1 and searches for some records and moves to Project 2 without linking them. In this case, all the selection of Project 1 will be wiped off.

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

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.

image-20240917-114959.png

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

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

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.

image-20240918-132539.png

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.

image-20240807-130038.png

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.

image-20240807-130507.png

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 

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.

image-20240808-135516.png

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.

Platforms 

Release & Cycle

Reset to Not Run

Reset Assignee

Execution Status

Copy platform with selected Execution Status

Platforms 

Release & Cycle

Reset to Not Run

Reset Assignee

Execution Status

Copy platform with selected Execution Status