Import test cases with Excel

  Work in Jama > Work in projects > Import items > Microsoft Excel (XLS, XLSX, CSV) > Prepare Excel document for import >

Import test cases with Excel

Previous pageNext page Print this topic! Mail us feedback on this topic!

With a single spreadsheet, you can import multiple Test Cases and their corresponding Test Steps. There are two approaches to using Excel for bringing test cases into Jama: one-way imports to quickly bring legacy test cases into Jama or round-trip imports that let you work with Jama content outside of Jama and bring changes back in safely. Here are a few things to keep in mind.

One-way import for Test Cases

Follow the same instructions as a One-way Import using the Data Import Wizard.

When importing Test Cases and their Test Steps your Excel spreadsheet MUST contain at least the following four column headers:

Test Case Name
Expected Results

The example below shows a document that would import two Test Cases: one called 'Test Wheel', the other 'Test Brakes'. Each row where the Test Case Name is repeated will be imported as a new Test Step.



In order for Jama to read the Test Steps, you must select the Header Row as Row 2, so that the mappings begin with the first test step rather than the field names.


Round-trip for Test Cases

Performing a round-trip import for Test Cases works just like a regular round-trip. Because of the relationship between Test Cases and Test Runs, there are some caveats to editing Test Cases from round-trip.

While you can update, add, remove, or re-assign a Test Case in a round-trip, you cannot update the Test Case Status this way. This is because the Test Case Status field is calculated from all of the Test Runs derived from that Test Case.

Add a Test Step

1.Copy a pre-existing row.
2.Insert the copied cells where appropriate. You must insert the copied cells rather than pasting directly over the cells. Otherwise, you will replace the row instead of adding a new row and subsequent steps will be removed on import.



3.Make needed changes to the copied fields.

Note: The numbering of the steps will appear off, but will re-number upon import.

Remove a Step

Remove a step anywhere in the sequence of steps. Re-numbering takes effect upon import.