Skip to end of metadata
Go to start of metadata

You can import XLS or XLSX files directly in Adaptavist Test Management using a simple Wizard. To do this, click on the Test activity in the navigation bar and then click on New>Import from file.


You can download (Sample1.xlsx) to use as a template for creating your own.

Importing Steps

You can import the script type (Step-by-Step) by creating a column for the Step and another column for the Expected Result according to the sample below:

You can import the script type (Plain Text) by creating a column for the Plain Text  according to the sample below:

Importing limitations

  • Importing data from Microsoft Excel does not calculate/evaluate formulas.
  • Only the first (left-most) worksheet tab of an Excel workbook will be imported (eg: Sheet1).
  • Excel time cells are not allowed (must change manually the format to Text).

Settings

Below is a table of all settings you can adjust before importing your XLS or XLSX file.

Setting
Description
Destination folderSelect the destination folder to import your Test Cases.
Date formatSelect the date format used on your Test Cases.
Date separatorSelect the Date separator used on your Test Cases.
Start import at rowSelect the first row to start importing the test cases.
This row contains the field nameIndicates if the row contains fields names or data.

Importing system fields

Below is a table of all system fields that are importable via the XLS or XLSX. Fields in bold are required.

Field Name
Description
Name

Text field single line.

Ex: Validate mandatory fields.

Precondition

Text field multiline.

Can contain line breaks.

Html tags will be imported.

Ex: Leaves fields in blank to verify if user can advance without filling mandatory fields.

Objective

Text field multiline.

Can contain line breaks.

Html tags will be imported.

Ex: Make sure the user is unable to proceed further without filling mandatory fields.

Test Script (Step-by-Step) - Step

Text field multiline.

Can contain line breaks. Should not be used if the Test Script (Plain Text) field has been mapped.

Html tags will be imported.

Ex: Leave username field in blank and attempt to proceed further.

Test Script (Step-by-Step) - Test Data

Text field multiline.

Can contain line breaks. Should not be used if the Test Script (Plain Text) field has been mapped.

Html tags will be imported.

Ex: Access code: 1533.

Test Script (Step-by-Step) - Expected Result

Text field multiline.

Can contain line breaks. Should not be used if the Test Script (Plain Text) field has been mapped.

Html tags will be imported.

Ex: User is unable to proceed further, page warns about mandatory field.

Test Script (Plain Text)

Text field single line.

Should not be used if any Test Script (Steps) field has been mapped.

Ex: The content of the error message should be "field user name is mandatory".

Folder

Folder structure separated by slash (/).

Ex: "folder 1/folder 2" or "/folder 1/folder 2" (same effect for both options).

Non-existing folders will be created.

Folders that match existing ones (including all path) will be merged.

Status

Name or short sentence describing the value.

A value mapping step will be available for such fields.

Ex: "Draft", "Approved", "In Review".

Priority

Name or short sentence describing the value.

A value mapping step will be available for such fields.

Ex: Low, Medium, High.

Component

Name or short sentence describing the value.

A value mapping step will be available for such fields.

The component field is the same component used by the JIRA's project.

Ex: Manufacturing

Labels

Name or short sentence describing the value.

A value mapping step will be available for such fields.

Ex: Functional, Non-Functional, Smoke, Integration, Automated, Manual

Owner

The key of existing JIRA users.

If user doesn't exist, it will not be imported and a warning will be generated.

Ex: ccaetano

Estimated Time

The estimated time in seconds or using format hh:mm.

Excel time cells are not allowed (must change manually the format to Text).

If the value can't be parsed, it will not be imported and a warning will be generated.

Ex: 00:40 or just 2400 (seconds).

Coverage

A issue key list, separated by comma (,).

If an issue doesn't exist for a given key, it will not be imported and a warning will be generated.

Ex: TIS-490, WOR-351


Importing custom fields

Below is a table of all custom fields that are importable via the XLS or XLSX file.

Field Type
Description

Single Line

Any value without line breaks. Html tags are not parsed.

Multi Line

Can contain line breaks. Html tags will be imported.

Checkbox

Accepts value true, false or boolean Excel cells.

Decimal Value

Decimal numbers using dot (.) as separator or number Excel cells.

If the value can't be parsed, it will not be imported and a warning will be generated.

Number Value

Integer numbers or number Excel cells.

If the value can't be parsed, it will not be imported and a warning will be generated.

Select List

Name or short sentence describing the value.

Non-existing items will be created.

Date Picker

Date using the date format configured during the import wizard or date Excel cells.

If the value can't be parsed, it will not be imported and a warning will be generated.


Procedure

1. Open the Import from file option by clicking on the drop down located on the New test case button.

2. Select the desired option and follow the steps.


  • No labels