Import test cases from Microsoft Office

If you have test cases written in Microsoft Word or Microsoft Excel, you can import existing documents to Polarion, creating Test-Case type artifacts in projects which can then be tracked and managed with project workflows. If you import from Microsoft Word, you create a new LiveDoc document, creating Test-Case-type Work Items according to rules you set up to recognize such artifacts from the original document content. If you import from Microsoft Excel, you can import in two ways. If you prefer a document-based approach, import into a LiveDoc Document. If you prefer a tool-based approach, import into the integrated tracker.

For more detailed information on importing information to create Work Items, see Import Work Items.

Import multivalued data

You may want to specify data in an Excel worksheet to be imported into multivalued fields in Polarion. For example, the Category field can contain multiple values. Your project might also have some multivalued custom fields. If properly formatted in the Excel sheet, the Polarion importer recognizes multiple values and imports them correctly. You can format multiple values in two ways:

  • Specify each value in a cell under the column for the field, and merge that column to span all the values.

  • Specify all values in a single cell under the column for the field, separating each value with a comma character.

You have two alternatives for formatting Excel data for import to Polarion multivalued fields

Merge field cell, OR...

Comma-delimited multiple values

Recognition of multivalued data can be switched on or off in the import wizard using the Separate multiple values option. When this option is selected, delimited values in a mapped column are imported to Polarion as multiple values in the target field. Recognized delimiters are comma (,) and semi-colon (;) characters. Detection of merged heading cells in Excel is automatic.

For reference information on supported fields, see Multivalued Data and Fields.

Define Test Steps in Excel

When defining Test Cases having discreet test steps, you can format your Excel worksheet in such a way as to facilitate import into Polarion. Here are a few tips:

  • Specify a column with a name like Title to identify each Test Case. You can include another column such as Description for the general description of each Test Case.

  • Define columns corresponding to those defined in your projects Test Step Columns configuration, for example, Step Name, Step Instruction, Expected Result.

  • Use one row for each step when writing up the test steps. Then, when these are complete, vertically merge the Title and Description columns so that they encompass the test step rows (see figure below).

    You may wish to leave an empty row between test cases. This can give you an additional import rule condition when importing your test cases.

When you import the Excel workbook, you can map test steps to the Test Steps field of Test Cases. For more information on importing from Excel and mapping columns to fields, see Import from Excel.

The following sections discuss creating new Work Items in existing Documents and the Work Item Tracker.