Introduction

Test Cases Module is the central repository of test cases. It allows users to create, organize, reuse, and manage test cases efficiently. A single test case can be used repeatedly and associated with multiple releases and cycles - avoiding the need to copy test cases. The execution status of test cases is independent per cycle allowing organizations to repeatedly execute the same test case 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 to Test Cases.

Test Case Module UI

The Test Case module screen has the following UI.

1. Create New Folder - Users can organize test cases into folders and subfolders for improved control and management.

Open

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

3. Include/Exclude Test Cases from Sub Folders at Parent Folder: Users can opt to include or exclude test assets from sub folders at parent folder. 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 on the test asset tree at left, and select deselect Include Entities from Sub-Folder.

4. Perform Bulk Operations on Folders - QMetry enables users to perform bulk operations for archiving, unarchiving, copying, and moving folders.

4. Auto Generate Test Cases - QMetry now enables users to automatically generate test cases using AI.

5. Create New Test Cases - Users can manually create test cases directly from the Test Case module UI.

6. Set Filters - Users can easily filter test assets by any system/custom fields on all module grids. It also helps users in carrying out bulk operations. Both basic and advanced filters can be applied to the records.

To apply advanced filters, these are the steps:

1. Click on the '+' button.

2. Select required filters.

3. Apply filter values.

4. Click ‘save and apply’.

For example, users want to filter test assets on Priority, and Entity Key. Click on the '+' icon and select the fields on the drop-down list. Users 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.

7. Reset Filters and Clear Filter Value - The "Clear Filter Values" option resets the values in the filter fields, allowing users to adjust criteria without recreating the filter, while the "Reset Filters" option returns all filter settings to their default state, removing any selected fields.

8. Manage Grid Columns - All grids within the Requirements, Test Cases, Test Suites, and Issues module have Arrange Columns option that allows users to create a customized view of their test assets. The view is saved for future use. The following customization can be applied:

• Show More Columns: The ability to add columns in the view. If there are other columns that you think important to display on the module grid apart from the default view, then you can just select those columns to add them to the view.

• Hide Columns: The ability to remove a column from view. If you do not want to include columns of less important on the module grid view, then remove column selection to hide those columns on the view. Users can show/hide the Testing Type field in the Test Case module.

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

• Re-arrange: The ability to 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: The ability to expand and reduce column width. If you want to display the full content of the column, then you may want to change the column width. To change the width of one column, just place the cursor in between the columns and drag the boundary on the right side of the column heading until the column gains the width that you want.

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.

Testing Type: The Testing Type field indicates how the test case was generated in QMetry: either 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.

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

10. 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, and more.

11. Operations on Individual Test Cases - Users can perform various operations on individual test cases, including move, copy, archive, create a new version, delete, stop watching, create a test suite, share as a child test case, and push the latest version to child test cases.

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

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

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

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

Adding a 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:

• Select the folder in the tree.

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

Deleting Test Case Folder

To delete a test case folder, follow these steps:

1. Select the folder on the tree and click the Archive button to archive it.

2. Once archived, the folder can be deleted.

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

A. Breadcrumb

On the Test Case Details page, users can return to the main test cases screen by clicking on the breadcrumbs.

B. Previous and Next Button

In addition to that, the Previous and Next buttons on the detail page are added for ease of navigation and updating the test cases.

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, Requirements, Release & Cycles, Test Executions, Issues, Version, Attachments, Comments, Change Log.

Each tab displays relevant details. The details are editable.

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.

Adding a Test Case 

Users can manually create test cases within a project, including details such as test steps, preconditions, and other relevant information.

To add a 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 and other necessary details.

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: Enter the name of the test case.

2. Priority: Assign priority level as—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: Users 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 at a time.

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

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.

User Defined Fields

If User Defined Fields (UDFs) are added for the test case module, they will be displayed on both the Create Test Case screen and the Test Case Details screen.

Test Steps

Users can add, view, edit, and delete test steps under a test case.

To add test steps, follow these instructions:

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

2. To add a test step, choose 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.

Risk Analysis

When creating a test case, users can input 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.

Once all details are entered and the Create button is clicked, the test case is saved, and the user is redirected to the Test Case module list view page. The newly created test case is automatically assigned a unique test entity key.

Editing/Updating a Test Case

Test cases can be updated directly, including parameters and test steps.

To edit a test case:

1. Use the in-place editor on the detail screens. Hover over the field and click the edit icon.

2. Make the necessary changes and save to update the test case.

• User Defined Fields: If UDFs are added to the test step module, then they are displayed on the Test Steps section as columns beside the default fields of test steps.

• Show/Hide and Re-arrange Test Step Columns - Users can customize the test steps panel by dragging and dropping columns to rearrange them and choose to show or hide columns like Input Data, Expected Outcome, and other User Defined Fields (UDFs).

Click Save to apply any changes made to the Test Steps panel.

Editing Test Steps

QMetry allows users to easily edit test case steps from the details page. Users can add new steps or modify existing ones.

1. Click the Edit button.

2. Click in the cell to modify the step. This action opens the test case details page in editable mode.

Alternatively, users can also edit the test step details by clicking on the Edit icon for the step.

The step section will expand to show system fields (Step Description, Input Data, and Expected Outcome) and custom fields. Users can switch between the fields.

• Large Text UDFs are displayed in separate tabs, while other UDFs are combined in a single tab named Other.

• Use the Move to Step button to return to the Step Description section.

• Navigate between steps using the Previous Step, Next Step.

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

• Click Apply to save changes.

Show/Hide and Re-arrange Test Step Columns

Users can customize the test steps panel by dragging and dropping columns to rearrange them. They can also choose to show or hide columns such as Input Data, Expected Outcome, and other User Defined Fields (UDFs). Click Save to apply any changes.

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 page

• Test Case Detail Page

• Create New Version page

• Exploratory testing

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.

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.

Removing Test Case Steps

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

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

Create a New Version of Test Case

When test steps are added or edited, the system will prompt to create a new version of the test case to preserve these updates. The test suite will continue to link to the previous version of the test case.

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

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.

Handling Test Case Execution Status

When saving a new version of a test case that has been previously executed, users have two options:

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 update to the latest version, click the sync button.

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

Archiving a Test Case

To delete a test case, all its versions must be archived. Once a test case is archived, users cannot perform further operations such as adding attachments, linking test cases, issues, or release cycles.

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

Users can also archive a test case from the test cases module list view. Please refer to the Test Case Module UI section above to know more.

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

To delete a test case, users are required to follow a two-step process: Archive the test case, and then delete it. Ensure that all versions of the test case are archived before proceeding with deletion.

Steps to Delete a Test Case

1. Archive the Test Case:

   • All versions of the test case must be archived. This action will prepare the test case for deletion.

2. Delete the Test Case:

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

A. Deleting from the 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, check the “Show Archived Items” box on the left panel.

2. Locate 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

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

Users can link requirements to their corresponding test cases, with each requirement linked to a test case only once. This linkage applies to all versions of the test case, ensuring that any updates to the test case maintain the requirement's relevance.

Purpose of Linking Requirements

Linking requirements to test cases provides context for what it being developed and how it should be tested. By associating test cases with specific requirements, testers gain clarity on the scope and objectives of the testing, ensuring that the developed features are thoroughly tested according to the defined requirements.

Link Requirements

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

Steps to Link Requirements

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

2. Click on the Link button.

3. It opens the Link Requirements pop-up with the list of test cases on it.

4. Select the specific requirements to be linked.

5. Users can filter, sort and search for specific requirements to be linked.

6. Click link and close.

Selecting Requirements Across Projects:

Execution runs are archived when the associated Platform, Release, Cycle, or Test Suite is archived. Archived test runs will be hidden on the Execution Runs tab if they are linked to these archived entities.

To view archived test runs, select the "Show Test Runs with Archived Platform(s)/Release(s)/Cycle(s)/Test Suite(s)" checkbox on the Test Executions tab.

Linking a Specific Version of a Requirement

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

Filter Options:

Users can use Filters to display criteria for filtering records within and across projects. Labels and Folder path filters 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 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. Click the Unlink icon next to the requirement to remove. Confirm the action when prompted.

3. To unlink multiple requirements, select the requirements and click the Unlink Selected button. Confirm the action when prompted.

Sync Latest Test Case Version with Requirements

To sync the latest version of a test case with its linked requirements, follow these steps:

1. Navigate to Test Case > Requirement tab.

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

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.

3. Sync with Multiple Requirements in Bulk:

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

   • Select the requirements to update.

   • Click the Sync Latest Version of Test Case button to synchronize the selected requirements with the latest test case version.

Confirmation

A confirmation pop-up will appear, asking if the user wants to sync the selected linked requirements with the latest version of the test case. Click Yes to proceed with the synchronization.

Upon successful synchronization, a confirmation message will appear. For bulk synchronization, the progress can be monitored 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

QMetry allows linking test suites via the Test Executions tab on the Test Case details page for thorough testing.

Linking Test Suites

Clicking the "Link Test Suites" button opens the test suite list view. Users can either scroll through test suites within the current project or select test suites from other projects to link to a specific test case.

To link Test Suites directly, these are the steps:

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

2. Users can link single as well as multiple test suites:

   • For linking a Single Test Suite, click the Link icon next to the test suite.

   • For linking Multiple Test Suites, select the desired test suites.

3. Click the Link Selected Test Suites 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:

1. Use the Project drop-down menu to select the desired project. Available test suites for the selected project will be displayed.

2. Ensure you have 'Modify' rights for the Test Suite module in the target project.

3. Select and link test suites for the chosen project. Note that your selections will be cleared when switching to another project.

Test suites from other projects will display their Entity Key. To view details, click the Test Suite Entity Key to open the test suite detail page in the respective project, which will switch your current project.

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 -

Filtering and Managing 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 reset filter criteria while keeping the field setup. Empty fields will include all records in the results.

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

Link Test Suites By Entity Key 

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

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.

View Linked Test Suites

The Test Executions tab will display the latest execution build for the linked test suites, helping QA Managers and Testers review the most recent build against which the test case was executed.

View Test Run Logs

Test run logs can be viewed and downloaded from the Test Executions tab on the test case details page. If a test suite has attachments, a blue Attachment icon will appear. Only attachments related to the specific test case will be displayed, providing detailed execution information 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: 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.

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. Select the test cases for bulk linking.

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

6. Click on Update.

Linking Issues to Test Cases

Users can link issues to test cases directly through the Issues tab on the test case details page, bypassing the test suite execution. Both internal and external tracker issues, such as those from Jira, can be linked.

Use Case: Suppose testers know that a particular issue or issues are related to a particular test case, and they don't want to execute the test case just to link those issues to it. Hence, they want a way to directly link issues to 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, users can utilize Basic and Advanced Filters to narrow down the search:

   • Basic Filters: Default fields for filtering.

   • Advanced Filters: Click the '+' icon to access additional system and user-defined fields for more detailed filtering.

4. Clear Filter Values: Resets filter values while retaining field settings, allowing for easy adjustments without removing fields.

5. Reset Filters: Restores default filter settings, removing all selected advanced filters.

Linking Issues Across Projects

Users can link issues from another project to a particular test case.

1. Select Project: Use the Project drop-down menu to choose a project. Issues from the selected project will be displayed.

2. Filter Issues: Apply filters to the selected project only.

3. Link Issues: Select the issues to link and click Link.

4. Create New Issue: 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. Refresh the Link Issues pop-up to view newly created issues.

The linked issues will appear on the Issues tab of the test case details page.

Issue Traceability in Test Case

In the Test Cases module, the Issues tab shows issues linked to the test case, either directly or indirectly through execution of the test case.

To view the issue of other project, click on the Issue Entity Key. It opens the issue detail page in the respective project and will change your current project.

You can identify whether the issue is linked from execution screen or from the test case detail page by looking at the Direct Linkage and Execution columns.

• Direct Linkage:

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