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.

Key Features of the Test Cases Module:

• Arrange Test Cases into folders and sub-folders.

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

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.

Filters

Filter requirements using system or custom fields across all modules. To learn more about filters, refer Filtering Assets document.

Folder Management

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

Bulk Operations

Perform bulk operations at the folder level within or across projects. To learn more, refer to the Bulk Operations document.

Test Case Module List View Columns

By default, the system displays the Entity Key, Summary, and Version columns. You can include additional columns such as Priority, Latest Execution Status, Testing Type, Dates, and counts for linked Requirements, Test Cases, Test Suites, and more from the Arrange Column Icon.

Click on the status to view further details of the test execution.

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.

Test Case Detail

To access the test case detail page, click the Test Case Entity Key in the grid view or Right-click the Entity Key to open it in a new tab. The requirement details page contains:

A. Individual Section Tabs (Editable)

B. Combined View (Read-Only View)

Managing Test Cases

You can create, edit, copy, move, archive, and delete test cases. Admins can grant permissions from Roles in the Customization screen.

Creating New Test Case 

You can create new test cases manually. Learn more about Creating New Test Cases.

Importing Test Cases

You can import test cases from Excel and Jira. Learn more about Importing Test Cases from Excel.

Editing Test Case Details

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

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.

To edit the steps with in-line editing, perform the following steps:

1. Go 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.

Editing or Updating Test Steps

You can edit the steps within a test case. This includes, editing existing steps, adding new steps, adding attachments to test steps, inserting shareable test case or copying steps from existing test cases.

To edit test steps, perform the following steps:

1. Click the ​Test Case Entity Key​​.

2. Go to the ​Test Steps​ tab and click ​Edit​​.

3. You get two options: In-line editing and test-step editing.

In-Line Editing

Hover over the cells to edit.

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

Test Step Editing

You can also update the details of a test step by clicking the edit icon next to that step.

Click the ​Edit​​ icon for a particular test step.

This allows you to edit the step description, input data, expected outcome and custom fields.

In the expanded view, the Large Text UDFs have seperate tabs while all other UDFs are combined in a single tab named ​Other​​. You can edit the fields within the ​Other​​ tab using in-line edit.

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:

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:

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

2. 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 or Removing Test Case Steps

You can delete unwanted test case steps by clicking the remove icon.

Deleting or Removing Test Steps in Bulk

To delete test steps in bulk, perform the following steps:

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.

Copying Test Cases

Copying a test case creates a duplicate, allowing you to reuse the test case across different folders and projects. When copying or moving test cases, you must select a destination folder.

If you don't select a folder, the system automatically places the copied test cases in the Root folder by default.

Moving Test Cases

You can move test cases within the current project, either individually or in bulk.

• From a Specific Folder
  When a test case is moved from a specific folder, it is removed from the source folder and added to the selected destination folder.

• From the Root Folder
  When a test case is moved from the Root folder, it is not removed from the Root folder but is instead added to the selected destination 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

You can edit a test case and save it as a new version. Read more about ​Creating New Test Case Versions​​.

Archiving a Test Case

Archiving removes test cases from all associated folders and moves them to a dedicated “Archived” bucket. To view archived test cases, apply Show Only Archived Test Cases filter in the test case list view.

Once you have archived a test case, 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:

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. The test case is archived after confirmation.

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:

1. Open the test cases module.

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

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

When unarchiving test cases, you can select one or more folders to associate.

To unarchive an archived test case, perform the following steps:

1. Click on filters

2. Select Show Only Archived Test Cases.

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

4. 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:

1. Archive the Test Case

   • All the versions of the test case must 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.

Deleting Test Cases

You can delete a test case from the Test Case List View or Test Case Detail Page.

To delete a test case, perform the following steps:

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

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

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

You can share the 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:

1. Open the Test Cases details page.

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

3. Enter one or more email addresses.

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 a Test Case

1. Open the test case details page.

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

3. You can share this link through 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.

To Link Requirements to a test case, perform the following steps:

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

2. Click Link.

3. It opens the Link Requirements screen, displaying a list of all available requirements.

4. 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 the Link and Close.

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 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 find the relevant requirements, you can apply filters on the requirement records. Labels and Folder path filters further aid in searching records.

Requirements of Release and Cycle of This Test Case

When viewing test assets of other projects, the Requirements of Release and 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.

To link requirements by entity key, perform the following 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 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:

1. Go 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 from the test case and click 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 Requirement tab under the Test Case module 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 (v3) is created. Users can sync the v3 of test case with the linked requirements.

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

To sync the latest test case version with a single requirement, perform the following steps:

1. Go to the Test Case module.

2. Select the Requirement tab.

3. Sync with a Single Requirement:

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

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

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:

1. Go to the Requirement tab on the Test Cases Detail Page.

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

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

4. Click Yes to proceed. Upon successful synchronization, a confirmation message will appear.

For bulk synchronization, you can monitor the progress in the Scheduled Tasks section. The selected requirements will be updated to reflect the latest version of the test case.

Linking Test Suites to Test Cases

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

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

To link test suites from other projects, perform the following 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 required project.

3. Available test suites for the selected project are 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.

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.

eSignature Considerations

The Project drop-down on the Link Test Suite screen will only show projects where eSignature settings align with linking permissions.

If the eSignature feature is enabled in the Project

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.

To link test cases by entity keys, perform the following 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 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 from the estimated time of all test cases in the test suite.

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

  • Not Run: Included in remaining time calculations.

  • Failed or Blocked: Considered as requiring further work.

  • Passed or Not Applicable: The Remaining time is adjusted accordingly.

Example

This section will illustrate how Execution Time and Remaining Time are calculated based on test case status and estimates.

Execution Time = 14

Remaining Time = 9

Linking Test Suites and Requirements in Bulk

QMetry enables users to link test suites and requirements to test cases in Bulk through the Test Case Bulk Operations.

To link test suites and requirements in bulk, perform the following steps:

1. Go to the Test Case module.

2. Click the cog icon to select Bulk Operations.

3. On the Bulk Operations screen, select Edit.

4. Select the test cases for bulk linking.

5. Choose specific Test Suites and Requirements from the available options.

6. Click 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.

Steps to Link Issues

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

2. Click the Link button to open the Link Issues pop-up, which displays a list of available issues.

3. For issues from Jira, you can customize the view using the arrange columns or filters options.

• The Advance Filter option is also available for the custom fields that are configured/mapped for the Issue module in Projects > Integration.

• The Arrange Columns option will show all the system and custom fields that are configured/mapped for the Issue module in Projects > Integration.

Users can link issues from another project to a particular test case as well. Here are the steps to link an issue from across projects

• Use the Project drop-down menu to choose a project. Issues from the selected project will be displayed on the screen.

• Select the issues that you want to link to the test case. You can also use the filter option to filter the list.

• If you're linking issues from multiple projects, ensure you select and link the issues from one project before switching to another, as any unlinked selections will be cleared when you switch projects.

• To add a new issue, select the current project from the drop-down and click Create New Issue.

• This opens the Issue module in a new tab. You can create a new issue and save it.

• Refresh the Link Issues pop-up to view newly created issues.

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

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

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 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 to it.

1. Click on the Add New button to associate release and cycle with the test case. The dropdowns 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.