How to import test cases and associations?

 

Overview:

You can import test cases from Excel (.xls, .xslx or .xlsm) or .zip format files.

These files must have a specific format, the import template can be downloaded in the application.

With an import file in Excel format you can import simultaneously test cases, test steps, parameters, datasets and the test cases/requirements associations.

The zip format import file allows you to import test cases and test steps.

 

This article will only focus on the import in Excel format. If you need information on the import in .zip format, you can check the dedicated page on our Wiki.

 

To import a test case file:

  1. Go to the test cases workspace
  2. Click on the [Import] button of the tree menu Bouton impor TC

  3. Click on “Import” in the drop-down menu:

  4. A window “Import Excel data” will pop up, you will be able to:

    • Choose the import format (Excel or zip), in this example it is Excel
    • Download the import templates for every format
    • Choose the file to import by clicking on [Choose file]
    • Import the file or simulate a file import

  5. After having clicked on [Import] or [Simulate] then confirmed, a window summarizing the import will pop up. The requirements import recap can be seen next to the “Requirement” line and the requirements/test cases association recap is next to the “Association” line.
    Finally, the one concerning the requirements/requirements links can be seen next to the “Links” line:

  6. If you chose the “Import” option, the requirements, the requirements/test cases associations and the requirements/requirements links will appear in the tree of the requirements workspace.

 

Here are some rules to follow when creating an Excel file:

  • The Excel file must have a table including columns as described hereafter in the table.
  • The data imported are materialized by a pair tag/value(s).
  • The tags are always placed on the first row (headers in the table), in whatever order.
  • The value(s) are placed in the row(s) that follow the first tag row.
  • The import is made row by row. The order does not matter.
  • The names of the fields in the first column are not case sensitive.
  • The empty rows are ignored.
  • The cells must not be merged.

 

Description of the import file 'LINK_REQ_TC' tab:

TAG Description

ACTION

(Mandatory)

Determines the action to realize. It must include the following values (or letters):

  • CREATE (C): when creating a test case
  • UPDATE (U): when updating a test case

TC_PATH

(Mandatory)

Test case path, from the project name to the requirement name
ex: /Project name/Folder name/Requirement name
TC_NUM Test case order in its folder
TC_REFERENCE
Test case reference
TC_NAME Test case name
TC_MILESTONE Name of the milestone(s) bound to the test case
TC_WEIGHT_AUTO Complete with 1 if weigh calculation is automatic
Complete with 0 if weigh calculation is manual
TC_WEIGHT Test case importance code:
VERY_HIGH, HIGH, MEDIUM, LOW
TC_NATURE Test case nature code:
ATDD, BUSINESS_TESTING, NON_FUNCTIONAL_TESTING, PERFORMANCE_TESTING, SECURITY_TESTING, UNDEFINED, USER_TETSTING
TC_TYPE Test case type code:
COMPLIANCE_TESTING, CORRECTION_TESTING, END_TO_END_TESTING, EVOLUTION_TESTING, PARTNER_TESTING, REGRESSION_TESTING, UNDEFINED
TC_STATUS Test case status code:
APPROVED, OBSOLETE, TO_BE_UPDATED, UNDER_REVIEW, WORK_IN_PROGRESS
TC_DESCRIPTION Test case description
TC_PRE_REQUISITE Test case prerequisite
TC_CREATED_ON Test case creation date
TC_CREATED_BY Creator login
TC_LAST_MODIFIED_ON Test case last modification date
TC_LAST_MODIFIED_BY Login of the user who last modified the test case
TC_CUF_<cuf code> Code of the custom fields bound to the test case

 

Description of the ‘SETPS’ tab of the import file:

Balise Description

ACTION


(Mandatory)

Determines the action to realize. It must include the following values (or letters):

  • CREATE (C): when creating a test step
  • UPDATE (U): when updating a test step

TC_OWNER_PATH

(Mandatory)

Path towards the test case owner of the test step
TC_STEP_NUM Order of steps (by numbers)
TC_STEP_IS_CALL_STEP Complete with 0 if step is a step action
Complete with 1 if step is a call step
TC_STEP_CALL_DATASET INHERIT: if the chosen option is not to choose datasets, in that case, the calling test case will inherit the parameters of the called test case
<name>: gives the chosen dataset
TC_STEP_ACTION Step action or path towards the called test case if it is a call step
TC_STEP_EXPECTED_RESULT Expected result for the step
TC_STEP_CUF Code of the custom fields bound to the test step

 

Description of the ‘PARAMETERS’ tab of the import file:

Balise Description

ACTION
(Mandatory)

Determines the action to realize. It must include the following values (or letters):

  • CREATE (C): when creating a parameter
  • UPDATE (U): when updating a parameter

TC_OWNER_PATH

(Mandatory)

Path towards the test case owner of the dataset
TC_PARAM_NAME
Parameter name
TC_PARAM_DESCRIPTION Parameter description

 

Description of the ‘DATASETS’ tab of the import file:

Balise Description

ACTION
(Mandatory)

Determines the action to realize. It must include the following values (or letters):

  • CREATE (C): when creating a dataset
  • UPDATE (U): when updating a dataset

TC_OWNER_PATH

(Mandatory)

Path towards the test case owner of the dataset

TC_DATASET_NAME

(Mandatory)

Dataset name
TC_PARAM_OWNER_PATH
Path towards the test case owner of the parameter.
This column is necessary in the case of parameters coming from test cases called bu the test case owner of the dataset.

TC_DATASET_PARAM_NAME

(Mandatory)

Parameter name for which the value will be filled
TC_DATASET_PARAM_VALUE
Corresponding value for the specified pair {dataset | parameter


Description of the ‘LINK_REQ_TC’ tab of the import file:

Balise Description

REQ_PATH

(Mandatory)

Requirement path from the project name to the requirement name

REQ_VERSION_NUM

(Mandatory)

Number of the requirement version to link

TC_PATH

(Mandatory)

Test case path from the Project name to the test case name