Import Test Cases

Introduction

The Import Test Case feature helps you import test cases from an Excel file (CSV/XLSX format) file into QMetry Test Management for Jira app. 

Use Case: An organization has its test cases documented in an excel file, now they have chosen QMetry Test Management for Jira app and want to import their test cases into QMetry.

Permissions Required

Jira Permissions:

  • Browse Project permissions are required.

QMetry Permissions:

If QMetry permissions are enabled, the following permissions are required.

  • Import Permissions

  • All Test Case Permissions (except Delete)

  • Configuration Modify Permission - Users can create labels, components, new values for custom fields via import.

If QMetry Permissions are not enabled, then users with Project Access permissions can import test cases to the project.

Where to Find the Feature

  1. Go to the QMetry menu > Test Management > Test Case tab.

  2. Click on the Import button at top right.

Note: If QMetry permissions are enabled, the Import button will be enabled only if the users have both Import and Test Case Create permissions. (In the case of QMetry permissions are enabled.)

Steps to import test cases from a csv/xlsx format

  1. Upload File

  2. Map Fields

  3. Import

Note: You can import a test case file with a maximum of 5000 rows for test cases and steps.

Step 1. Upload File

  • Download Template.xlsx below for your reference. Ensure the file you are importing should be as per the format as QMetry format. 

Browse / Drop File:

You can either

  • Browse and select the excel file to upload or

  • Drag the excel file and drop it in the specific area on the screen

 

  • Select Sheet: Once you upload the file, the drop-down starts showing the sheets included in the file.

  • Destination Folder: It displays the default path of the selected folder on the Test Case folder tree. This is the path wherein the test cases will be imported. You can change the import folder path by selecting another folder path on the drop-down list.

  • Date Format : This option is available only in case the import file is in CSV format. This option allows to choose the date format used for the Date type column from the CSV file.

  • If a Test Case with the same key already exists in the system, then:

    • Import with New Version: This will create a new version of your existing Test Case.

      • Note: If QMetry permissions are enabled, the Import with New Version option will be enabled only if the users have the Test Case Versioning permission. (In the case of QMetry permissions are enabled.)

    • Skip: The test case will be skipped.

  • If Test Case fields like components, labels do not exist in the project:

    • Create: New values for the list will be created in QMetry for Jira.

      • Note: 

        • If QMetry permissions are enabled, the Create option will be enabled only if the users have the Configuration Modify permission. (In the case of QMetry permissions are enabled.)

        • Fix Version, Sprint, Assignee, Reporter will not be created.

    • Ignore: New values in the excel file will be imported as blank and existing values will be imported.

Click Next.

Step 2. Map Fields

  • There are two columns on the screen: QMetry Field and Sheet Field. Map the Sheet Fields with QMetry Fields. Enable Auto Mapping to auto map the fields.

  • The field values in excel will be imported into QMetry for Jira accordingly. (Custom fields can be mapped)

  • QMetry Fields marked with * are mandatory to be mapped with Sheet Field.

  • If the system fields and custom fields are marked as mandatory under the Configuration section, then make sure these fields are not blank in the Excel sheet.

 

Folder

In addition to the Destination Folder Path selected in Step# 1, you can import test cases in the Folder Paths defined in the Excel file. This folder path is mentioned in a specific column in the Excel file. You can also mention multiple folder paths to import test cases to multiple folders at a time. It helps users import the test cases in multiple folders at a time so that they can avoid repeated imports of the same test cases. If the folder field is not mapped, then the test cases will be imported in the Destination Folder path selected in step #1. If the folder field is mapped, then the test cases will be created in the folders under the Destination Folder path selected in Step #1.If the folder doesn’t exist, then the folders will be auto-created as per the hierarchy set in the folder path set in the actual file.

  • Multiple comma-separated (,) folder paths can be mentioned in the column. For example, If you want to import test cases in folder A and folder B, here is how the folders should be mentioned in the import file: Folder A,Folder B.

  • Folder path containing sub-folder can also be mentioned. For example, “Configuration/Device Configuration”.

  • If the Folder Path mentioned in the sheet exists under the selected Destination Folder, then the test cases will be imported under the existing folder(s). So make sure you select the Destination Folder in Step #1 accordingly.

  • If the Folder Path mentioned in the sheet does not exist under the Destination folder, then new folders will be created under the Destination Folder Path that you selected at Step# 1 above. So make sure you select the Destination Folder accordingly.

For the Folder QMetry field, select the excel sheet column in the Sheet Field in which the folders are mentioned.

 

Story Linkages

QTM4J provides an ability to link test cases with relevant Jira stories (i.e. Jira issue type mapped as Story) while importing the test cases through an excel sheet using the Import Test Case feature. The mentioned stories should be available in Jira.

A column Story Linkages is added to the import test case sheet. You can also find the column when you export existing test cases to excel. You can re-import the excel sheet with story keys filled in.

Define the Issue Key in this column, which should be mapped at Step# 2 of Map Fields while importing test cases. The defined key is then linked to the test case that is being imported.
To link multiple stories in a test case at a time, define comma-separated Issue Keys in the Story Linkages column.

The feature is helpful when users have bulk test cases to import and also have to link stories with these test cases.

Permissions: Users should have Requirement Edit permission to import test cases with Story Linkages.

For the Story Linkages QMetry field, select the excel sheet column in the Sheet Field in which the Story Keys are mentioned.

Import Test Cases with Parameterized Steps

QTM4J provides the ability to import test cases with parameterized steps while importing test cases through Excel. If the parameters already exist in the Configuration section of the project, they will be reused. If the parameters are not available in the Configuration section of the project, they will be created in the section.

Use Case: Testers need to import test cases some of which have parameterized steps within them in Excel. The team needs to import parameters along with test case and step data in one go so that they can avert spending time on adding those parameters individually.

Required Permissions:

  • Configuration Modify permissions

  • Test Case Edit permissions

Steps

  • The syntax of parameterized step to be used in the Excel file is [~Parameter_name]. For example, [~Username].

  • When Excel has test cases with existing parameters imported, then the parameters are reused in the steps and associated in the Parameters section in the Steps tab on the test case detail page.

  • When Excel has test cases with parameters that do not exist in the project in QTM4J is imported, then the parameters will be auto-created in the project, if the user has the necessary permissions to create the parameters. If the user does not have the required (Configuration Modify) permissions, the new parameters in the steps will be displayed as a normal text string and shall not be created.

Note: This feature is not applicable to shared test cases in the project.

 

Once you are done with mapping the fields, click on the Start Import button.

Step 3. Import

The bar on the screen shows the progress of the test case import.

Click Done when the import process is over.

Limitations

  • Attachments can not be imported. They should be attached from the UI once the test cases are imported.

Import Test Cases with Shareable Steps

Refer to https://qmetrysupport.atlassian.net/wiki/spaces/QTM4J/pages/3199206018/Shareable+Test+Cases?src=search#Import-Test-Cases-with-Shareable-Steps for more details.