Introduction

Test Cases Module is the central repository of test cases. This module enables you to create, organize, reuse, and manage test cases efficiently.

In QMetry, you can use a single test case repeatedly. A test case can be linked to multiple requirements and test suites as well as associated with multiple releases and cycles. The execution status of test cases is independent per cycle allowing organizations to repeatedly execute the same test case for different cycles without affecting the test results between separate runs.

Open

Key Features of the Test Cases Module:

• Organize Test Cases into folders and subfolders.

• Add and Edit Test Cases.

• Import Test Cases from Excel and Jira.

• Execute Test Cases for ad-hoc testing.

• View the Status of individual Test Cases.

• Link relevant Requirements and Issues to Test Cases.

• Set Predecessor and Successor relationships between Test Cases.

Test Case Module UI

The Test Case module screen includes the following UI elements. The functionalities of each of these features are explained in detail in the later part of the document.

New Folder

You can create a new folder or a sub-folder to organize test cases for improved control and management.

Open

Sorting and Clear Sorting

You can sort the folder structure either alphabetically or by date (newest first or oldest first).

Include/Exclude Test Cases from Sub Folders at Parent Folder

You can include or exclude test assets from sub folders at parent folder level. By default, Include Entities from Sub-folder remains selected, and entities from sub-folders are displayed at parent folder level on the module list view.

To hide the entities from sub-folder, open the Options drop-down, and select deselect Include Entities from Sub-Folder.

Perform Bulk Operations on Folders

You can perform bulk operations for archiving, unarchiving, copying, and moving folders.

Auto Generate Test Cases

QMetry now supports auto-generation of test cases using AI.

Create New Test Case

You can manually create test cases directly from the Test Case module UI by clicking on the New button.

Filters

You can easily filter test assets by any system or custom fields across all module grids. Basic filters like Summary, Release, and Cycle are available by default. For advanced filtering, click the "+" icon to add custom filter fields.

To apply advanced filters, these are the steps:

1. Click on the '+' icon (Refer below image).

2. Select the desired fields for filtering.

3. Enter the filter values.

4. Click ‘Save and Apply’.

For example, you want to filter test assets by 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.

Reset Filters and Clear Filter Value 

The Clear Filter Values option provides users with improved flexibility, efficiency, and usability in managing and reusing Advanced Filters for important data that may not be easily accessible by default. This option only clears out the values in the filters without removing the fields themselves. It enables users to start fresh with the same set of fields, allowing them to adjust their filter criteria without having to recreate the entire filter setup each time. It preserves empty fields in the filter just like fields with values and allows users to easily modify and refine the filter criteria without losing the content of the set fields. Here, empty fields in the filter will consider all records.

The Reset Filters option will reset the filter to default. All the selected fields for Advanced Filter will be removed from the filter.

Manage Grid Columns

All grids within the Requirements, Test Cases, Test Suites, and Issues module have Arrange Columns option that allows you to create a customized view of the test assets. The view is saved for future use.

The following customizations can be applied to the grid view:

• Show Columns: You can customize the grid view by adding necessary columns. To display additional columns beyond the default view, select the relevant fields from the "Arrange Columns" section.

• Hide Columns: You can remove columns from the grid view. If certain columns are not needed, deselect them to hide them from the module grid.

  • Users can show/hide the Testing Type field in the Test Case module. If users want to use their own UDF instead of this field, they can hide it. The setting is provided in the Manage Fields section of the Customization module. Refer to Manage Fields for more details.

• Search: Quickly locate specific fields using the search box.

• Re-arrange: Arrange the columns in a different order through drag and drop functionality.

• Select All: This will add all available columns to the view.

• Clear All: This will remove all columns except the default ones.

• Restore Default: Revert to the default column settings.

• Resize Columns: Adjust column width as needed to display the full content. To modify the width of a column, position the cursor between two column headers and drag the boundary on the right side until the desired width is achieved.

Test Case Module List View Columns

You can customize the columns in the list view to meet your specific needs. By default, the Entity Key, Summary, and Version columns are displayed. You also have the option to include additional columns such as Priority, Latest Execution Status, Testing Type, Dates, and counts for linked Requirements, Test Cases, Test Suites, and more, enabling a personalized view.

Latest Execution Status

Users can view the Latest Execution Status column in the Test Case List View. This column indicates the current execution status based on settings configured under: Home > Customization > Execution Status. Refer Execution Status Management to know more.

Upon selecting the Latest Execution Status field, the column will be displayed in the grid view, indicating the most recent execution status of the test case, which may include options such as Blocked, Failed, Passed, Not Run, or Not Applicable.

Testing Type

The Testing Type field indicates how the test case was generated in QMetry: Manual or Automated. Test cases created through the UI or imported from Excel are classified as Manual, while those created via Automation APIs are marked as Automated. This field is read-only and cannot be edited.

Import/ Export

The Import option allows users to import test cases from Excel and Jira, while the Export option enables users to export selected test cases to Excel, CSV, Word, or PDF formats. Learn more about Importing Test Cases from Excel or Exporting Test Cases.

Bulk Operations on Test Cases

QMetry empowers users with the ability to efficiently perform bulk operations on test cases, such as editing, copying, archiving, unarchiving, deleting, sharing, deleting and more.

Operations on Individual Test Case

You can perform various operations on individual test cases, such as moving, copying, archiving, creating a new version, deleting, stopping notifications (stop watching), creating a test suite, sharing as a child test case, and pushing the latest version to child test cases by clicking the cog icon.

Managing Test Case Folders

QMetry allows testers to organize and manage test cases in a Folder-based hierarchy. Testers can group related test cases and organize them systematically during authoring or post-authoring.

It helps to carry out bulk operations like Move, Copy, Editing, Deleting, and Executing all test cases under one folder.

The count of test assets in the folder hierarchy is displayed alongside the folder name. The count includes active + archived test cases + shareable test cases.

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

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

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

Below are the actions users can perform on test case folders:

Creating Test Case Folder

To add a new test case folder, these are the steps:

1. Click the New Folder button on the Test Case module toolbar.

2. Enter the folder name and click Create. The new folder will appear in the tree.

Editing a Test Case Folder

To edit an existing test case folder, these are the steps:

1. Select the folder in the tree.

2. Click the Edit icon on the toolbar to open the folder detail screen in editable mode.

3. Edit the folder name and click on update.

Deleting Test Case Folder

To delete a test case folder you need to archive it first.

1. Select the folder on the tree

2. Click the Archive button.

3. Click Yes to archive the folder.

4. After archiving the folder, navigate to the filters section.

5. Click on the "Show Archived Items" checkbox.

6. The archived folder(s) will be displayed in the folder section.

7. Click on the archived folder.

8. Click the delete icon to remove it.

Test Case Detail Page UI

The Test Case Detail Page can be accessed from the Test Case module grid view by clicking on the Test Case Entity Key.

To open the test case detail page in a new tab/window, right-click on the Test Case Key in grid view. Opening test cases in different tab/browser makes a comparison between test cases easier. It also provides quick reference while working on multiple assets.

Navigation

QMetry facilitates seamless navigation within the test cases. You can easily move to the previous or next test case or access the complete list of test case through the test case module.

A. Breadcrumb

You can return to the Test Case module screen by clicking on the breadcrumbs.

B. Previous and Next Button

The Previous and Next buttons on the detail page assists in easy navigation.

Organize Tabs

The detail page of QMetry assets has different tabs on it. Users can customize the view of the detail page by changing the order of tabs. The tab order is preserved per user. 

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

Tabbed View vs. Combined View

The test case detail page displays -

A. Individual Section Tabs (Editable)

B. Combined View (Read-Only View)

A. Individual Section Tabs

There are individual tabs for - Steps, Details, Dependent Test Cases, Requirements, Release & Cycles, Test Executions, Issues, Version, Attachments, Comments, Change Log, and Children. Each tab displays relevant details. You can edit/modify a test case from this screen.

B. Combined View (Read Only View)

The tab displays the consolidated information about the entire test case.

Managing Test Cases

QMetry empowers users with comprehensive tools for managing test cases, allowing them to perform a variety of operations such as creating, editing, copying, moving, archiving, and deleting. Let’s have a detailed look at these features.

Create New Test Case 

You can manually create test cases within a project, incorporating details such as test steps, preconditions, and other pertinent information.

To add a new test case, follow these steps:

1. Click the New button on the Test Case module toolbar.

2. In the Add Test Case screen, enter system fields, test steps, user defined fields, risk analysis fields (described in detail below)

3. Click the Create button to save the test case.

System Fields, Test Steps, User Defined Fields and Risk Analysis

When creating a test case, users should enter specific details related to the test case. Let’s review the fields to understand what information to include.

System Fields:

In the System Fields section, users must enter the following details:

1. Summary: Provide a brief overview of the test case, outlining its purpose.

2. Priority: Assign a priority level to the test case, selecting from the options: Minor, Major, Blocker, Critical, or Trivial.

3. Labels: Choose one or more labels from the list to classify the test case.

4. Status: Select a status from the list. Statuses can be set to - New, Approved, In Progress, and Ready to Review.

5. Owner: Select the owner from a drop-down list displaying QMetry users with access to the current project.

6. Test Case Category: Categorize the test case appropriately as Regression, Performance, Security, Functional etc.

7. Estimated Time: Specify the estimated execution time for the test case in minutes.

8. Description: Add appropriate descriptions providing sufficient information about the feature. Users can add the description in Plain Text or Rich Text.

• Rich Text: Use the Rich Text Editor to format text, insert images, hyperlinks, and tables, ensuring all critical details are included.

• Adding Images: You can add multiple images simultaneously. Images can be added by:

  • Entering an Image URL.

  • Browsing the Desktop to upload an image.

  • Copying and pasting the image directly into the description box. Multiple images can be copied and pasted.

Use Case: An organization is using Rich text for Description field, in which they copy-paste the content from their source in html/xml format. Click on the Edit icon at the right to open the source editor.

You can view added images by clicking on them within the description box.

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 custom fields are added to the test case module from Customizations > Manage Field for this project, they will appear in this section.

Adding Test Steps

You can add, view, edit, and delete test steps within a test case.

Steps:

1. Go to the Steps section on the Create Test Case screen.

2. To add a test step, select one of the following methods:

   • Hover over the Step Description cell and click the Edit icon (pencil). Alternatively, use the TAB key to navigate.

   • Click the + icon on the right and select Insert Row to add a new step.

   • Click the settings icon for the current test step and select Insert Row to add a new step next to it.

3. A blank row will be added with an auto-generated step number. Enter the Step Description, Input Data, and Expected Outcome in the respective fields.

4. Repeat the process to add additional steps as needed.

To Insert a New Row

• To add a new row, click on the ‘+' icon and select 'Insert Row’. Alternatively, use the Tab key on your keyboard to navigate.

• Repeat the process to add additional steps as needed.

To Insert Shareable Test Case:

• Click on the cog ( ) icon for the current test step and select ‘insert shareable test case’.

• Select the shareable test cases from ‘Link Shareable Test Case’ Screen and click on link.

To Copy Steps from an Existing Test Case

• Click on the cog ( ) icon for the current step and select ‘Copy Steps from an Existing Test Case’.

• Click on the relevant test case and select the steps to be copied.

• Click 'Copy' or 'Copy & Close'.

User Defined Test Step Fields

If UDFs are added to the test steps, then they are displayed on the Test Steps section as columns beside the default fields of test steps.

These UDFs are set from Customizations > Manage Field. Refer Creating user-defined fields for Test Case for more information.

Show/Hide and Re-arrange Test Step Columns

You can organize the test steps columns in the panel through drag and drop operation. You can also opt to hide/show Input Data, Expected Outcome and other UDF columns on the screen.

Click Save once you make any changes to the Test Steps panel.

Any changes in test steps column arrangement will reflect in other places where the test steps panel is used. For example, column arrangement changes on the Execution screen will reflect in the following places.

• Test Case Create Screen

• Test Case Detail Screen

• Create New Version Screen

• Exploratory Testing Screen

Edit Entered Test Steps

While creating test cases, you can go back to a previous test step and make necessary modifications.

Steps

1. There are two ways in which you can edit a test step -

   1. Click on the Edit icon at the right.

   2. Hover over the test description, input data or expected outcome and the edit icon will appear. It allows you to do inline editing in the field.

2. Make necessary changes and press tab or click anywhere on the screen.

Risk Analysis

When creating a test case, you can enter risk analysis details including - Risk Type, Risk Category, Likelihood, Impact. Based on these values, the system automatically calculates the risk priority number, and the extent of testing required. These values help in setting the priority of the test cases in the right order.

After entering all the required details, click the Create button. The test case will be saved, and you will be redirected to the Test Case module list view page. The newly created test case will automatically be assigned a unique Test Entity Key.

Editing/Updating a Test Case

Click on the Test Case Entity Key for the test case you want to modify.

Editing/Updating Test Case Steps

To edit test case steps, navigate to the steps tab and locate the Edit button in the top-left corner. Clicking this button provides two editing options: in line editing and test step editing.

Inline Editing

You can edit the test case steps - step description, input data, expected outcome and other user defined fields directly by hovering over and clicking on specific cells.

Steps:

1. Navigate to the cell you want to update.

2. Hover over the desired cell to display it in editable mode.

3. Click on the cell and make the necessary modifications directly in the field.

Steps for Test Case Editing

Users can also edit the test case steps by clicking on the Edit icon for a particular test step.

Clicking on this edit icon will open the step section displaying (Step Description, Input Data, and Expected Outcome) and custom fields. You can switch between the fields.

In expanded view, the Large Text UDFs have separate tabs while all the other UDFs are combined in single tab named Other.

Other tab: UDFs other than Large Text appear in a combined view, where you can edit the fields inline.

You can perform the following actions on this screen:

• To go back to the Step Description section, click on the Move to Step button.

• You can use the Previous Step and Next Step buttons to navigate to the previous/next steps.

• Use the New Step button to add a new step next to the current step.

• Once you are done with editing the test step, click Apply to save the changes.

Actions on Test Step Cog icon

Users can perform the following actions on the Steps grid:

• Insert Row: Add a new step at the end or next to the current step.

• Insert Shareable Test Case: Add a shareable test case.

• Remove Row: Delete the selected step.

• Duplicate Row: Copy the selected step.

• Move: Change the position of the step by selecting a new index.

• Copying Steps from an Existing Test Case: Copy repetitive steps from an existing test case for reuse.

Copy Steps from an Existing Test Case

The 'Copy Steps from an Existing Test Case' option displays a list of all test cases within the current project. To copy steps from a different project, select a desired project from the top-left section of the screen.

When copying test steps from another project, all system-defined column values will be copied, while only the user-defined field (UDF) values that are common between the two projects will be included. Any user-defined fields that are not shared between the projects will be excluded from the copy.

You can refine the test case list using the filter option, allowing you to filter based on summary, release, cycle, test case status, or test case folder.

To view the steps within a test case, click the ‘+' icon next to the test case key. Select the required steps and click on 'copy or copy and close’.

Changing the Order of Test Case Steps

While executing test suite, the test case steps appear in the same sequence as arranged in the test case.

To reorder test case steps:

1. On the Steps tab, click the cog icon at the right of the step.

2. Select Move and choose the new index for the step.

Adding Attachments to Test Steps

Attachments can be added to provide additional data or resources, such as an Excel sheet with test data.

To add attachments:

1. Navigate to the test case detail page.

2. Open the Steps tab.

3. Click the Attachment icon for the relevant test step.

4. The Add Attachment screen will open. Attach the required files.

Downloading Attachments

• Single Attachment: Click the Download icon for the specific attachment.

• All Attachments: Click Download All. The zip file can be downloaded from the Schedule Task section, accessible via the icon on the application header.

Deleting Attachments

• Single Attachment: Click the Delete icon for the specific attachment.

• Multiple Attachments: Select the attachments and click Delete Selected.

Delete/Remove Test Case Steps

Users can delete unwanted test case steps by clicking on the remove icon option.

Delete/Remove Test Steps in Bulk

1. Select the test steps that you want to delete. The Delete button gets enabled on the selection of test step(s).

2. Click on the Delete button.

3. Click Update.

Editing/Updating Test Case Details

You can edit the values of both system-defined and user-defined fields from the Details tab.

Steps:

1. Navigate to the test case 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.

Dependent Test Cases

You can establish test case dependencies from the Dependent Test Cases tab in the test case details screen to manage the execution order. This ensures a logical and organized testing process, as one test case's execution depends on the successful completion of another. For more information, refer to Test Case Dependencies.

Create a New Version of Test Case

If test case steps are added or edited in the test case, which is already executed, then it is recommended to save the test case with Save as New Version. You can choose between updating the existing test case or creating a new version. Updating will overwrite the previous details, while creating a new version retains the original values in older version and incorporates the new changes by creating a New Version.

The Save as New Version button is visible on the screen only if you have versioning rights.

To save changes as a new version:

1. Create a New Version: Use the "Save as New Version" button to create a new version of the test case with the updated details.

   • Option A: Click on the Cog icon for the test case and select Create New Version.

   • Option B: Open the Test Case Detail Page and click on the Create New Version icon on the header.

2. Save as New Version: Make the required changes and click "Save as New Version" to create an updated version of the test case.

If you add/edit test steps within a test case, it will ask you to create a new version of the test case to save the content of steps along with test case parameters. The associated test suite will still be associated with the previous version of the test case.

Handling Test Case Execution Status

If the test case was executed before, then the following option is provided while saving the new test case version.

1. Auto Sync Latest Version:

   • If selected, the test case version will be updated, and its execution status will reset to “Not Run” on the Test Run screen.

   • Example: If TC1 previously had a “Passed” status in TS1, and the user updates TC1 and creates a new version, then TS1 will display TC1’s status as “Not Run.”

2. Manual Sync:

   • If auto sync is not selected, a sync icon will appear beside the current version of the test case on the Test Run screen.

   • To execute the latest version of the test case, you can click on the sync icon.

   • A confirmation message will appear, confirming the reset of execution status.

Archiving a Test Case

All the versions of the test case should be archived to delete that particular test case.

Once a test case is archived, you cannot perform any operations like adding attachments, linking test cases, issues, and release - cycles on an archived test asset.

A. Archiving from the Test Case Detail Page

To archive a test case from detail page:

1. Open the test case details page by selecting the test case.

2. Click the Archive icon located at the top right corner of the page.

3. Upon confirmation, it will archive all the underlying versions of the test case.

B. Archiving from Test Case module list view

To archive a test case from test case module list view page:

1. Open test cases module.

2. The test case list view opens with list of existing test cases within the project/folder.

3. Click on the Cog icon for the test case you want to archive and select Archive. The test case is archived after confirmation.

Archiving a Specific Test Case Version

To Archive a Specific Test Case Version, read the document: Archiving a Specific Test Case Version 

Unarchiving a Test Case

To unarchive an archived test case, follow the below steps:

1. Click on filters

2. Select “Show Archived Items”.

3. Click the cog icon next to the archived test case.

4. Click Unarchive.

Deleting Entire Test Cases

To delete an entire test case, users are required to follow a two-step process: Archive the test case, and then delete it.

Steps to Delete a Test Case

1. Archive the Test Case:

   • All the versions of the test case should be archived to delete that particular test case.

2. Delete the Test Case:

   • This will permanently delete the test case, including all its archived versions.

A. Deleting from Test Case Detail Page

Users can delete a test case directly from the test case details page.

Steps to delete test case from detail page:

1. Open the detail page of the archived test case. Use the filter on the tree to view archived test cases.

2. Click the Delete icon located at the top right corner of the screen.

3. Confirm the deletion in the pop-up dialog.

B. Deleting from the Test Case List View

Users can also delete a test case from the Test Case List View.

Steps to delete a test case from Test Case List View:

1. To view archived test cases, select the Show Archived Items check box in the filters section.

2. It displays archived test cases along with other test cases.

3. Search for the archived test case you want to delete.

4. Click the Cog icon next to the archived test case and select Delete.

Deleting a Specific Test Case Version

For instructions on deleting a specific test case version, refer to the section Deleting a Specific Test Case Version

Share Test Cases with Other Users

Share Test Cases

QMetry allows easy sharing of test cases with other users. Users can share the test case summary and test case link for easy access to the latest version.

Steps

1. Open the 'Test Cases' details page.

2. Click on the Share icon at the top (refer the image below).

3. Enter one or more email address(es).

4. Write a message (optional but recommended) describing the test case or required actions.

5. Click on the Share button.

Copy Test Case Link

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

URL Syntax

Steps to Copy Test Case

1. Open the test case 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.

The test case link is copied to the clipboard. Users can share this link with team members who need to work on the test asset, using email, chat, or other communication methods.

Bulk Operations on Test Cases

Read Bulk Operations

Linking Requirements to Test Cases

In QMetry, you can link requirements to the corresponding test cases to ensure traceability, allowing testers to validate that all requirements are covered by test cases and easily track testing progress.

This linkage applies to all versions of the test case, ensuring that any updates to the test case maintain the requirement's relevance.

→ Use Case: Users link requirements with related test cases for testing. Testers get the idea of what is developed by studying requirements and on that basis, they write test cases to describe how to test the developed application. Thus, linking the test case with the requirement gives relevance between the two what is developed and what to test.

Link Requirements

Requirements can be linked to a test case through the Requirements tab available on the Test Case Details page and Test Case Edit Page.

Steps to Link Requirements

1. Go to the Requirements tab of the test case details page or test case edit page.

2. Click on the Link button.

3. It opens the Link Requirements pop-up displaying a list of all available requirements.

4. You can filter the requirements, sort the requirements or manage view as needed.

You can link single requirement or multiple requirements to a test case.

• For linking a Single Requirement, click the Link () icon on the right.

• For linking Multiple Requirement, select the desired requirements and click on Link and Close button (as shown in the above image).

You can also link multiple requirements from different projects to a single test case.

Linking Requirements Across Projects

To link multiple requirements from different projects, follow these steps:

• Select Project from the Project drop-down in the top-left corner.

• The associated requirements for the selected project will be displayed.

• Tick the checkboxes next to the relevant requirements.

• After selecting the requirements from one project, click Link before switching to another project.

• Once all requirements are linked, click Link and Close.

Selecting Version

To link a specific version of a requirement, expand the requirement and select the specific version.

Filtering Requirements

To easily find the relevant requirements, you can apply basic as well as advanced filters on the requirement records. Labels and Folder path filters further aid in searching records.

Requirements of Release & Cycle of this Test case

When viewing test assets of other projects, the Requirements of Release & Cycle of this Test case checkbox remains unavailable. For test cases within the same project, this check box enables the users to view only those test cases that are associated with the same Release and Cycle to which the test case is linked.

Link Requirements by Entity Key 

This feature allows users to link requirements to a test case using comma-separated requirement entity keys.

Steps

1. Go to the Requirements tab of the test case.

2. Click on the Link By Entity Key button.

3. It opens the Link Requirements pop-up. Mention comma-separated Requirement keys.

4. Click Link.

The requirements with mentioned keys get linked to the test case.

View Linked Requirements

The linked requirements are shown on the lower grid pane.

If requirements linked are from other projects, the Entity Key of the corresponding project will be displayed. Click on the Requirement Entity Key to view the requirement detail page in the respective project.

Unlinking Requirements from a Test Case

To unlink requirements from a test case, follow these steps:

1. Navigate to the Requirements tab on the test case details page.

2. To unlink a single requirement: Click the Unlink icon next to the requirement to remove. The requirement is unlinked after confirmation.

3. To unlink multiple requirements, select the requirements you want to unlink from the test case and click on the Unlink Selected button.

Sync Latest Test Case Version with Requirements

You can sync the latest version of the test case to its linked requirements individually or in bulk. The sync feature in the Test Case > Requirement tab allows you to sync the test case version with individual requirements or with multiple requirements.

For example, the current version of the test case is v2. All the requirements are linked to this version of the test case. Now, a new version of the test case is created i.e., v3. Users can sync the v3 of test case with the linked requirements.

(A) Sync Latest Test Case Version with a Single Requirement

Steps:

1. Navigate to Test Case > Requirement tab.

2. Sync with a Single Requirement:

   • When a new version of the test case is available, the sync icon under the Test Case Version column turns blue.

   • Click on this blue sync icon to sync the latest version of the test case with the requirement.

This action ensures that the linked requirement is aligned with the most recent version of the test case.

(B) Sync Latest Test Case Version with Multiple Requirements in Bulk

If multiple requirements are linked to a test case and a new version of the test case is available, you can bulk sync all linked requirements to the latest test case version.

Steps:

1. Navigate to Test Case > Requirement tab.

2. Select the requirements to which you want to sync the latest test case version.

3. Click the Sync Latest Version of Test Case button.

4. A confirmation pop-up will appear, confirming if you want to sync the selected requirements with the latest version of the test case. Click Yes to proceed.

Upon successful synchronization, a success message will appear on your screen.

Linking Test Suites to Test Cases

In QMetry, you can link test suites to the corresponding test cases through the Test Executions tab on the Test Case Details Page or the Test Case Edit Screen.

Test Suites are linked to the test case in multiple Platforms associated with it.

Clicking the "Link Test Suites" button opens the test suite list view.

Filtering, Managing and Arranging Test Suites

• Filter Values: User can apply multiple criteria to filter test suite records within and across projects.

• Clear Filter Values: This option allows users to remove chosen filter values while retaining the fields. Empty fields will include all records in the results.

• Reset Filters: Reset filter restores the filter to its default state, removing all selected fields from the filter.

• Manage View: Users can opt to show/hide particular columns, resize column widths and customize their view through the arrange columns option.

Linking Test Suites within Same Project:

1. Open the Test Executions tab and click the Link Test Suites button.

2. On the Link Test Suite pop-up, you can link single or multiple test suites:

   • For linking a Single Test Suite, click the Link () icon on the right.

   • For linking Multiple Test Suites, select the desired test suites and click on Link and Close button.

The linked test suites will appear on the Test Executions tab of the test case details page.

Linking Test Suites Across Projects:

To link test suites from other projects these are the steps:

1. Open the Test Executions tab and click the Link Test Suites button.

2. On the Link Test Suite pop-up, click on the project drop-down menu to select the desired project.

3. Available test suites for the selected project will get displayed.

4. Select and link test suites for the chosen project by clicking the link button.

5. Once all the test suites are linked, click ‘Link and Close’.

View Linked Test Suites

All test suites linked to the test case are displayed in the ‘Test Executions' Tab. To view the details of a linked test suite, click on the 'Test Suite Entity Key’.

If the test suite belongs to another project, the Entity Key of the corresponding project is displayed. Clicking the entity key will open test suite details page in that respective project.

View Archived Test Runs

An execution/test run is archived when the associated Platform, Release, Cycle, or Test Suite is archived. Once a Platform, Release, Cycle, or Test Suite is archived, any test executions linked to them will not be displayed on the Test Executions tab of the test case.

To view archived Test Runs, select the Show Archived Records checkbox in the filter options (as shown in image below).

eSignature Considerations

If the eSignature feature is enabled in the Project -

Link Test Suites by Entity Key 

This feature allows users to link test suites using comma-separated test suite entity keys.

Use Case: The feature is useful when you have a list of test suite entity keys that you need to link to a test case. You can use this option to link the test suites directly without having to search for each test suite individually.

Steps:

1. Go to the Test Executions tab of the test case.

2. Click the Link Test Suites by Entity Key button.

3. Enter comma-separated test suite keys in the pop-up.

4. Click Link to associate the specified test suites with the test case.

The Test Executions tab shows the last execution build for the test suite. It is useful when a QA Manager/Tester wants to see the latest Build against which the execution was done on the 'Test Executions' tab of the Test Case screen.

View Test Run Logs

Test run logs to test cases are attached at the test run level. These logs are available on the Test Executions tab of the test case details page. If a test suite has an attachment(s) attached to it, then the Attachment icon is displayed in blue color for that test suite. Only test case-level attachments will be displayed here.

The attachments at the test run level are displayed to provide more in-depth information on test case execution. Users can get the execution details of the test case on the same screen.

Click on the Blue attachment icon. It opens the Attachments pop-up as below.

Execution Time & Remaining Time

On the Test Case detail page, within the Test Executions tab, users can view the Execution Time and Remaining Time for each test execution. These metrics help in test planning and estimation.

Use Case: Calculation of Execution Time and Remaining Time for the test suite is useful for the QA Manager in Test Planning as it gives accurate estimates for the test suite. These test case level estimates are refined each time a test suite is executed. Testers can make recommendations to have the test estimates revised based on the last few executions in different environments.

Two columns Execution Time and Remaining Time are added to the grid at the following places in the application:

• Test Suite detail page > Test Executions tab

• Test Case detail page > Test Executions tab

• Issue detail page > Execution Runs
  
  

Calculation:

• Execution Time: Calculated based on the Estimate Time of all the test cases in that test suite.

• Remaining Time: Once the test suite is executed, the Remaining Time Is calculated for all “Not Run” test cases.

  • Failed or Blocked: Any test case with “Failed” or “Blocked” status will also be considered as the work still remains on it.

  • Passed or Not Applicable: The Remaining Time will be reduced for test cases with “Pass” and “Not Applicable” status accordingly.

Example

The following example illustrates how Execution Time and Remaining Time are calculated based on Test Case Status.

Execution Time = 14

Remaining Time = 9

Linking Test Suites and Requirements in Bulk

QMetry enables you to link test suites and requirements from multiple projects in bulk through the Test Case Bulk Operations.

Steps:

1. Navigate to the Test Case module.

2. Click on the cog icon to select bulk operations.

3. On the Bulk Operations screen, select Edit.

4. Check Link Requirements or Link Test Suites as per your need.

5. Choose specific records from the available options.

6. Click on Update.

Linking Issues to Test Cases

The Issues tab in the test case details screen displays all issues linked to the test case from the test execution screen. You can also link issues directly to a test case without executing it, this includes internal as well as external tracker issues. This makes tracking of issues related to the test case easier.

→ Use Case: Testers have verified that the issues are related to a specific test case and prefer not to execute the test case solely for the purpose of linking those issues. Therefore, they require a method to directly associate issues with a test case.

Steps to Link Issues

1. Navigate to the Issues tab on the test case details page or test case edit page.

2. Click the Link button to open the Link Issues pop-up, which displays a list of all available issues. The link issue screen also provides you with all options like applying filters, resetting or clearing filters, sorting, resizing or managing columns.

3. Once all the issues are selected, click on link and close.

Issue Traceability in Test Case

In the Test Cases module, the Issues tab displays all issues linked to a test case, either directly or indirectly through test case execution. Clicking on the Issue Entity Key will navigate you to the Issue Details Page. If the issue belongs to a different project, clicking the entity key will automatically switch you to that project.

You can determine whether an issue is linked from the execution screen or from the test case detail page by checking the Direct Linkage and Execution columns -

• Direct Linkage Column:

  • If the issue is linked from the test execution (i.e. issue linked while execution of the test case), then the Direct Linkage shows “No”.

  • If the issue is directly linked to the test case, the Direct Linkage shows “Yes”.

• Execution Column:

  • The Execution column on the Test Case > Issues tab shows the count of test executions the issue has been linked to.

  • Clicking on the count opens the Execution Runs pop-up with execution details of the issue, executed Platform, Release, Cycle, Linkage Level, etc.

  • The Linkage Level column shows the issue is added on test case level or test step level on the execution screen.

When Jira is integrated with QMetry

• If an issue from Jira is directly linked with the test case, it will appear in the Issues tab of the test case.

• In Jira, the test case details will appear in the Test Case section of the linked Jira issue. The Test Case Steps tab will display step details of the test case. The Executions tab will remain blank as the Jira issue is linked with the test case without its execution.

• On the Jira add-on page, the Test Case Details tab will display all the details, while the Executions tab will appear blank.

Associate Release & Cycles

Release and Cycle can be associated from the test case detail page as well as the test case edit page.

The tab allows users to associate release and cycle to the test case. One test case can be associated with multiple releases and cycles. Release and Cycles are added from Projects > Project/Release/Cycle.

Once the test case is added, the user wants to add it to a particular Scope - release and cycle. For this reason, they edit the test case and associate the new release and cycle to it.

1. Click on the Add New button to associate release and cycle with the test case. The drop-downs are enabled by clicking on the Add New button.

2. Select the release(s); the cycle list is prompted for the selected release.

3. Select the cycle(s).

4. Select the version of the entity to associate as you can link releases and cycles to a particular version of the test case.

5. Click Save.

The associated release and cycle appear in the grid on the screen.

To remove the release and cycle association for the test case, click on the Unassociate button for the release and cycle combination.

Test Case Versions

Read about Test Case Versions

Change Log

Read about Change Log

Import Test Cases

Import Test Cases from Excel

Export Test Cases

Read Exporting Test Cases

Export Test Case Detail in PDF

Read Exporting Test Cases

Best Practice Recommendations

Tip #1: Before Adding test cases establish rules to how test cases are to be designed, categorized, and organized. QMetry comes with a number of system fields. All of the fields, along with the folders can help teams better manage their test cases. In addition, the Status field can be used to create a workflow to improve the development of the test cases from "New" to "Approved".

Tip #2: QMetry allows testers to provide actual results and record status at a test case level which may change how you design test cases moving forward. Teams should properly define how and when to add test case steps.