Back to QMetry All Products Help Page
Test Cases Module
- 1 Introduction
- 2 Test Case Module UI
- 3 Managing Test Case Folders
- 4 Test Case Detail Page UI
- 5 Managing Test Cases
- 5.1 Create New Test Case
- 5.2 Importing Test Cases
- 5.3 Editing/Updating a Test Case
- 5.4 Dependent Test Cases
- 5.5 Archiving a Test Case
- 5.6 Archiving a Specific Test Case Version
- 5.7 Unarchiving a Test Case
- 5.8 Deleting Entire Test Cases
- 5.9 Sharing Test Cases with Other Users
- 5.10 Bulk Operations on Test Cases
- 6 Linking Requirements to Test Cases
- 7 Linking Test Suites to Test Cases
- 8 Linking Test Suites and Requirements in Bulk
- 9 Linking Issues to Test Cases
- 10 Associate Release & Cycles
- 11 Test Case Versions
- 12 Change Log
- 13 Import Test Cases
- 14 Export Test Cases
- 15 Export Test Case Detail in PDF
- 16 Best Practice Recommendations
Introduction
The Test Cases module is the central repository of test cases. This module enables you to create, organize, reuse, and manage test cases.
In QMetry, you can use a single test case repeatedly. You can link a test case to multiple requirements and test suites as well as associate it with multiple releases and cycles. The execution status of test cases is independent per cycle which means you can repeatedly execute the same test case for different cycles without affecting the test results between separate runs.
Permissions
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 grid view offers various customization options.
Sorting and Clear Sorting
You can sort the folder structure alphabetically or by date (newest first or oldest first).
Sorting
Clear Sorting
Filters
You can 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.
Basic Filters
Advanced Filters
A. Basic: By default, test cases can be filtered by summary, release, and cycle. Enter specific values in these fields to retrieve test cases that match the specified criteria.
B. Advanced: You can also apply advanced filters to refine the test cases based on fields beyond the basic options.
To apply advanced filters, perform the following steps:
Click on the “+” icon.
Select the desired fields for filtering.
Enter the filter values.
Click Save and Apply.
For example, you want to filter test assets by Priority and Entity Key.
Click 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.
Note
Filtered views are automatically saved for future use, eliminating the need to reapply the same filters repeatedly.
Reset Filters and Clear Filter Value
The Clear Filter Values clears out the values in the filters without removing the fields themselves.
The Reset Filters option will reset the filter to default. All the selected fields for Advanced Filter will be removed from the filter.
Reset Filters
Clear Filter Values
Manage Grid Columns
The Arrange Columns option in the Test Case Module grid enables you to customize the asset view. Refer to the Manage Grid Columns page to know more.
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.
Latest Execution Status
You 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 Customization on the Execution Status tab.
Refer to 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.
Click on the status to view further details of the test execution.
Notes
The Latest Execution Status can be calculated once every 24 hours per project.
After generating the status, the Generate button will be disabled for the next 24 hours.
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.
Managing Test Case Folders
You can organize and manage test cases in a folder-based hierarchy. You can further group related test cases and organize them systematically during authoring or post-authoring.
It helps to carry out bulk operations like - Move, Copy, Edit, Delete, and Execute 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
Folder B (5) <------Child Folder
Folder C (2) <------Subfolder of Child Folder
Include/Exclude Test Cases from Sub-Folders at the Parent Folder
You can include or exclude test assets from subfolders at the parent folder level. By default, Include Entities from Sub-folder remains selected, and entities from Sub-folders are displayed at the parent folder level on the module list view.
To hide the entities from the sub-folder, open the Options drop-down and deselect Include Entities from the 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 Case Detail Page UI
Click the Test Case Entity Key in the grid view to open the test case detail page. Right-click the Entity Key to open it in a new tab.
Navigation
You can navigate through the test case module using Breadcrumb navigation or the Previous and Next buttons. See User Navigation for details.
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
With the necessary permissions, you can create, edit, copy, move, archive, and delete test cases. Admins can grant permissions from the Customization screen (Customization > Roles).
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 required information.
To add a new test case, perform the following steps:
Click New.
In the Add Test Case screen, enter system fields, test steps, user-defined fields, and risk analysis fields (described in detail below).
Click the Create button to save the test case.
System Fields, Test Steps, User Defined Fields, and Risk Analysis
When creating a test case, you need to 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, enter the following details:
Field Name | Description |
---|---|
Summary | Provide a brief overview of the test case, outlining its purpose. |
Priority | Assign a priority level to the test case: Minor, Major, Blocker, Critical, or Trivial. |
Labels | Choose one or more labels to classify the test case. |
Status | Select appropriate status: New, Approved, In Progress, and Ready to Review. |
Owner | Assign an owner from users with access to the current project. |
Test Case Category | Categorize the test case as Regression, Performance, Security, Functional etc. |
Estimated Time | Specify the estimated execution time for the test case in minutes. |
Description | Add a description in 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
Notes
To use rich text, enable the Enable Rich Text parameter for the Project from Project Management under the Projects tab.
Refer to Enable Rich Text Editor for more details.
Rich Text: Use the Rich Text Editor to format text, and 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.
Notes
The supported file formats of the image are JPG, JPEG, PNG, and GIF.
The maximum file size should be 1 MB for images uploaded through browsing.
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.
You can also download the added image by clicking on the image and then selecting the Download icon in the top right corner.
User-Defined Fields
If custom fields are added to the test case module from Customizations under Manage Fields tab 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.
Permissions
Permissions are managed through Customization under the Roles tab, where user roles are assigned specific rights for Test Case operations.
You can perform these actions based on the permissions granted to their roles.
To add new test steps, perform the following steps:
Go to the Steps section on the Create Test Case screen.
Click the expand icon to view test steps in full-screen mode.
Hover over the right end of the row to display the edit pencil and cog icon.
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 cog icon for the current test step and select Insert Row to add a new step next to it.
A blank row is added with an auto-generated step number.
Enter the Step Description, Input Data, Expected Outcome, and other UDF details in the respective fields.
Repeat the process to add additional steps as needed.
Note
Test steps support both Plain Text and Rich Text.
To insert a Shareable Test Case, perform the following steps:
Click on the cog ( ) icon for the current test step and select Insert Shareable Test Case.
Select the shareable test cases from the Link Shareable Test Case Screen and click on the link.
To Copy Steps from an Existing Test Case, perform the following steps:
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.
Alternatively, you can also insert shareable test case or copy steps from an existing test case by clicking on the “+” icon.
User-Defined Test Step Fields
If you have added UDFs to the test steps, then they are displayed on the Test Steps section as columns beside the default fields of test steps. You can set UDFs from Customizations under the Manage Field tab.
Refer to 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 the 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 a New Version Screen
Exploratory Testing Screen
Editing Entered Test Steps
While creating test cases, you can go back to a previous test step and make necessary modifications.
To edit the entered steps, perform the following actions:
There are two ways in which you can edit a test step -
Click on the Edit icon at the right.
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.
Make necessary changes and press the tab or click anywhere on the screen.
Risk Analysis
Note
To enter risk analysis details, the super admin must first enable the risk analysis field for the project from Project Management under the General Settings tab.
When creating a test case, you can enter risk analysis details including, Risk Type, Risk Category, Likelihood, and 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.
Test cases are added at the Project level. The Test Case module's main screen shows test cases according to the selected folder.
Importing Test Cases
You can import test cases from Excel and Jira. Learn more about Importing Test Cases from Excel.
Editing/Updating a Test Case
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.
Note
In-place edits will update the existing test case without creating a new version.
To edit the steps with in-line editing, perform the following steps:
Navigate to the cell you want to update.
Hover over the desired cell to display it in editable mode.
Click on the cell and make the necessary modifications directly in the field.
Steps for Test Case Editing
You 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 the step description, input data, expected outcome, and custom fields. You can switch between the fields.
In the expanded view, the Large Text UDFs have separate tabs while all the other UDFs are combined in a 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 Rows
Insert Row
Insert Shareable Test Case
Copy Test Steps from an Existing Test Case
You can also perform these actions on a specific test step by clicking the cog icon at the right end of the row.
Actions on Test Step Cog icon
You 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.
Copying 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 the 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.
Notes
Shareable Test Cases added as Steps cannot be copied.
Steps from shareable test cases can be copied from the filtered list when Show Only Shareable Test Case is selected.
A copy icon will highlight the copied steps, and hovering over the icon will display details of the source test case.
An info icon appears for copied steps. Hovering over the icon displays attachment-related details in a tooltip. Attachments are copied along with the steps, but they will only become visible and editable after saving the copied steps.
Changing the Order of Test Case Steps
While executing the test suite, the test case steps appear in the same sequence as arranged in the test case.
To reorder test case steps, perform the following steps:
On the Steps tab, click the cog icon to the right of the step.
Select Move and choose the new index for the step.
Adding Attachments to Test Steps
You can add attachments to test case steps either by clicking the attachment button for a test step or by embedding attached images/files in rich text fields.
Read Managing Attachments to know more
Deleting/Removing Test Case Steps
You can delete unwanted test case steps by clicking on the remove icon option.
Deleting/Removing Test Steps in Bulk
To delete test steps in bulk, perform the following steps:
Select the test steps that you want to delete. The Delete button gets enabled on the selection of test step(s).
Click on the Delete button.
Click Update.
Editing/Updating Test Case Details
You can edit the values of both system-defined and user-defined fields from the Details tab.
To update the test case in bulk, perform the following steps:
Navigate to the test case details screen.
Access the Details tab.
Hover over the values you wish to edit.
Enter the new values and click the checkmark to save your changes.
Note
Changing the folder path moves the asset to a different folder.
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.
Creating a New Version of the Test Case
Permissions
Ensure your role includes versioning rights.
The admin can configure versioning rights from the Customization screen under the Roles tab.
If test case steps are added or edited in an already executed test case, save it as a new version to retain the original details. Updating overwrites the previous details, while creating a new version preserves the original values and creates a new version of the test case with updated details.
The Save as New Version button is visible on the screen only if you have versioning rights.
To save changes as a new version:
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.
Save as New Version: Make the required changes and click Save as New Version to create an updated version of the test case.
Option A: From Cog Icon
Option B: From the Test Case details Page
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.
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.”
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 the execution status.
Notes
The synced version does not show previously linked issues.
After syncing, the execution status of the test case will change to "Not Run."
Any new test steps added in the latest version are reflected on the execution screen.
You can use different versions of a test case for testing.
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 the detail page, perform the following steps:
Open the test case details page by selecting the test case.
Click the Archive icon located at the top right corner of the page.
Upon confirmation, it will archive all the underlying versions of the test case.
B. Archiving from the Test Case module list view
To archive a test case from the test case module list view page, perform the following steps:
Open the test cases module.
The test case list view opens with a list of existing test cases within the project/folder.
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, perform the following steps:
Click on filters
Select Show Archived Items.
Click the cog icon next to the archived test case.
Click Unarchive.
Deleting Entire Test Cases
Deleting a test case is a two-step process: Archive the test case and then delete it.
To delete a test case, perform the following steps:
Archive the Test Case
All the versions of the test case should be archived to delete that particular test case.
Delete the Test Case
This will permanently delete the test case, including all its archived versions.
A. Deleting from Test Case Detail Page
You can delete a test case directly from the test case details page.
To delete a test case from the detail page, perform the following steps:
Open the detail page of the archived test case. Use the filter on the tree to view archived test cases.
Click the Delete icon located at the top right corner of the screen.
Confirm the deletion in the pop-up dialog.
B. Deleting from the Test Case List View
You can also delete a test case from the Test Case List View.
To delete a test case from the Test Case List View, perform the following steps:
To view archived test cases, select the Show Archived Items check box in the filters section.
It displays archived test cases along with other test cases.
Search for the archived test case you want to delete.
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
Sharing Test Cases with Other Users
You can share test case summary and test case link with other members of the team for easy access to the latest version.
To share a test case, perform the following steps:
Open the “Test Cases” details page.
Click on the Share icon at the top (refer to the image below).
Enter one or more email addresses.
Write a message (optional but recommended) describing the test case or required actions.
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
https://<URL>>/#/<AssetType>/<AssetKey>
For example,
Steps to Copy a Test Case
Open the test case details page.
Locate and click on the Copy Link icon ( ) on the breadcrumb navigation.
Users can share this link via any preferred communication channel.
You can share this link with team members using email, chat, or other communication methods.
Bulk Operations on Test Cases
Read Bulk Operations
Linking Requirements to Test Cases
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.
Linking 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.
To Link Requirements to a test case, perform the following steps:
Go to the Requirements tab of the test case details page or the test case edit page.
Click on the Link button.
It opens the Link Requirements screen, displaying a list of all available requirements.
You can filter the requirements, sort the requirements, or manage the view as needed.
You can link a single requirement or multiple requirements to a test case.
For linking a Single Requirement, click the Link () icon on the right.
For linking Multiple Requirements, 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, perform the following 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 the Link before switching to another project.
Once all requirements are linked, click Link and Close.
Note
If you're linking requirements from multiple projects, ensure you select and link the requirements from one project before switching to another, as any unlinked selections will be cleared when you switch projects.
Selecting Version
To link a specific version of a requirement, expand the requirement and select the specific version.
Filtering Requirements
To 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.
Linking Requirements by Entity Key
This feature allows users to link requirements to a test case using comma-separated requirement entity keys.
Notes
A maximum of 500 entities can be linked at once.
The requirement key will be ignored if a relevant requirement with that key is not found.
If a single key is mentioned multiple times, it will be linked only once.
If an older version of the requirement is already linked and you are linking the same requirement key, then the latest version will not replace the older version. It will be skipped.
Archived versions will be skipped from linking. Only the latest unarchived version of entities will be linked.
To link requirements by entity key, perform the following steps:
Go to the Requirements tab of the test case.
Click on the Link By Entity Key button.
It opens the Link Requirements pop-up. Mention comma-separated Requirement keys.
Click Link.
The requirements with the mentioned keys get linked to the test case.
Viewing Linked Requirements
The linked requirements are shown on the lower grid pane.
If the 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:
Navigate to the Requirements tab on the test case details page.
To unlink a single requirement: Click the Unlink icon next to the requirement to remove. The requirement is unlinked after confirmation.
To unlink multiple requirements, select the requirements you want to unlink from the test case and click on the Unlink Selected button.
Syncing the 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) Syncing the Latest Test Case Version with a Single Requirement
To sync the latest test case version with a single requirement, perform the following steps:
Navigate to Test Case > Requirement tab.
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) Syncing the 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.
To sync the latest test case version with multiple requirements in bulk, perform the following steps:
Navigate to the Requirement tab on the Test Cases Detail Page.
Select the requirements you want to sync the latest test case version.
Click the Sync Latest Version of Test Case button.
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.
For bulk synchronization, you can monitor the progress in the Scheduled Tasks section. The selected requirement(s) will be updated to reflect the latest version of the test case.
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. You can customize the view using arrange columns, filters or other customization options.
Linking Test Suites within the Same Project
Open the Test Executions tab and click the Link Test Suites button.
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 the 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
Note
Users must have Modify rights for the Test Suite module in the target project from which the test suites are being linked.
To link test suites from other projects, perform the following steps:
Open the Test Executions tab and click the Link Test Suites button.
On the Link Test Suite pop-up, click on the project drop-down menu to select the required project.
Available test suites for the selected project are displayed.
Select and link test suites for the chosen project by clicking the link button.
Note
If you're linking test suites from multiple projects, ensure you select and link the test suites from one project before switching to another, as any unlinked selections will be cleared when you switch projects.
5. Once all the test suites are linked, click Link and Close.
Viewing 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 the 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 it 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 the image below).
While importing any change in the status of such archived test case executions will be ignored.
eSignature Considerations
eSignature in Current Project | eSignature in Test Suite Project | Can test suites be linked to the test case? |
---|---|---|
Disabled | Enabled
| No (The Project drop-down on the Link Test Suite screen will only show those projects which have eSignature feature disabled) |
Disabled | Disabled | Yes |
Enabled | Enabled | Yes |
Enabled | Disabled | Yes |
If the eSignature feature is enabled in the Project
Test Case Status | Can test suites of any project be linked to the test case? |
---|---|
Approved | Yes |
In Review | No |
Linking 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.
Notes
A maximum of 500 entities can be linked at a time.
Test suite keys not found will be ignored.
Duplicate keys are linked only once.
Archived test suites are skipped.
When "Skip Duplicate Linkage" is enabled, already linked test suites are excluded, linking only those not yet associated with the test case version from which the linking is being performed.
When "Skip Duplicate Linkage" is off, the test case version from where the test suite is being linked, that version will get linked to all the test suites
To link test cases by entity keys, perform the following steps:
Go to the Test Executions tab of the test case.
Click the Link Test Suites by Entity Key button.
Enter comma-separated test suite keys in the pop-up.
Click the 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.
Viewing 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 estimated 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.
Test Cases | Execution time | Status | Remaining time |
---|---|---|---|
TC1 | 2 | Pass | - |
TC2 | 3 | Not Applicable | - |
TC3 | 4 | Failed | 4 |
TC4 | 5 | Blocked | 5 |
14 | 9 |
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.
To link test suites and requirements in bulk, perform the following steps:
Navigate to the Test Case module.
Click on the cog icon to select bulk operations.
On the Bulk Operations screen, select Edit.
Check Link Requirements or Link Test Suites as per your need.
Choose specific records from the available options.
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 to link those issues. Therefore, they require a method to directly associate issues with a test case.
The count of total Issues Linked to a test case, whether linked directly from the issues tab or through execution, is displayed in the test case details page under the column ‘Linked Issue Count’.
Steps to Link Issues
Navigate to the Issues tab on the test case details page or test case edit page.
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.
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 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”.
Issues that are linked to executions can be unlinked from the execution screen.
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 whether the issue is added at the test case level or the test step level on the execution screen.
If the test case is associated with a requirement, then the issue directly linked to the test case will also appear on the Issues tab of that associated requirement.
When Jira is integrated with QMetry
If an issue from Jira is directly linked to 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 Project Management > Releases & Cycles.
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 with it.
Click on the Add New button to associate the release and cycle with the test case. The drop-downs are enabled by clicking on the Add New button.
Select the release(s); the cycle list is prompted for the selected release.
Select the cycle(s).
Select the version of the entity to associate as you can link releases and cycles to a particular version of the test case.
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
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 for how test cases are to be designed, categorized, and organized. QMetry comes with several 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.
Related content
Back to QMetry All Products Help Page