How to Upload Multiple Test Cases in Jira

Migrating to Jira Cloud? Join Dec ane^st webinar for strategies & tips. Learn more

Import from Excel is not supported in Zephyr Scale 7.2 and later. We'd suggest saving your Excel canvas to a CSV file and importing exam cases from this file. Run into Import Examination Cases From CSV for details. The information below about importing from Excel sheets applies to earlier Zephyr Scale versions.

You can import Excel files (.xlsx) directly into Zephyr Scale using a wizard.

If your information is in the Numbers spreadsheet program on a Mac OS, no worries! Only export to XLS before you proceed with the import process.

This topic is dissever into two main parts:

Annotation:

Having issues? Creating an Excel spreadsheet from scratch? Download the Sample1.xlsx template, which includes the suggested formatting.

Before y'all import: format your Excel spreadsheet

To import and allow you lot to map your fields and data accurately, the Excel spreadsheet you use to import your test-instance data needs to abide past a few formatting specifications.

Ascertain your examination steps

In that location are two ways y'all tin can format your examination steps. Cull one.

Option 1

Y'all can import the script type (Steps) by creating a cavalcade for Step and another cavalcade for the Expected Event, as demonstrated in the following example:

Click the image to overstate it.

Option two

Yous can import the script type (Manifestly Text) by creating a column for Test Script Patently Text, as demonstrated in the post-obit instance:

Import limitations

A few limitations to keep in listen:

• Importing data from Microsoft Excel does not summate/evaluate formulas.

• Just the commencement (left-most) worksheet tab of an Excel workbook will be imported (e.g. Sheet1).

• Excel time cells volition not import and must manually be changed to text format.

System fields available for import

This table lists all of the arrangement fields that are importable via Excel file.

Arrangement Field	Description
Name	Text field, single line. The Name field is required. Case: Validate mandatory fields.
Precondition	Text field, multi-line. May contain line breaks. Example: Leaves fields in blank to verify if a user can advance without filling mandatory fields.
Objective	Text field, multi-line. Can comprise line breaks. Case: Ensure the user is unable to proceed without filling mandatory fields.
Exam Script (Steps) - Step	Text field, multi-line. Can contain line breaks. Should not be used if the Exam Script (Plain Text) field has been mapped. Example: Leave username field blank and endeavour to keep further.
Test Script (Steps) - Expected Result	Text field, multi-line. Can incorporate line breaks. Should not be used if the Test Script (Plain Text) field has been mapped. Example: User is unable to continue farther. The page warns about a mandatory field.
Exam Script (Plain Text)	Text field, single line. Should not be used if whatsoever Test Script (Steps) field has been mapped. Example: The content of the error bulletin should be "field user name is mandatory."
Binder	Folder structure separated past a slash (/). Example: "folder one/folder 2" or "/folder 1/folder 2" (same effect for both options). Non-existing folders volition be created. Folders that match existing ones (including all path) volition be merged.
Condition	Name or brusque sentence describing the value. A value-mapping footstep volition be available for such fields. Example: Draft, Approved, In Review, etc.
Priority	Name or short judgement describing the value. A value-mapping stride will exist available for such fields. Example: Depression, Medium, High, etc.
Component	Proper 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 project. Example: Manufacturing
Labels	Name or short sentence describing the value. A value-mapping step will exist available for such fields. Example: Functional, Not-Functional, Smoke, Integration, etc.
Owner	The primal of existing Jira users. If the user doesn't exist, it will not exist imported and a alarm will be generated. Instance: ccaetano, jbond, etc.
Estimated Time	The estimated time in seconds or using format hh:mm. If the value can't be parsed, it will not exist imported and a warning will be generated. Example: 00:40 or just 2400 (seconds)
Coverage	An issue key list separated by a comma. If an outcome doesn't exist for a given key, it will non be imported and a warning will be generated. Instance: TIS-490, WOR-356, etc.

Importing your data to Zephyr Scale

1. Open up the projection yous desire to import the exam cases into, click Tests > Ellipses > Import from File.

   

   Click the paradigm to enlarge it.

   The Import from File sorcerer appears.

2. Click Microsoft Excel.
   The wizard progresses to the Setup phase.

3. Upload your Excel (.xlsx) file by dragging and dropping it into the defined expanse or by clicking Choose the File and selecting it from your local storage.
   Your file uploads to the wizard.

4. Consummate the fields in the Settings section.

   • Destination Folder - The folder into which you want to import your test cases. If a folder for your file does not exist in Zephyr Scale, i will be created during the import process.
     

   • Date Format (two fields) - The format your test cases use, including the separator (slash, nuance, or dot).
     

   • Start Import at Row - The row in which you desire the import to begin.

     Notation:

     The This row contains the field names checkbox is selected by default. Deselect this pick if the row specified does not comprise field names.

5. Click Adjacent.

   

   Click the image to enlarge information technology.

   The wizard progresses to the Field Mapping stage.

6. Map your fields, so click Side by side.
   Unmapped fields will not be created.

   

   Click the image to enlarge it.

   The wizard progresses to the Data Mapping stage.

7. Map your information type for components, priorities, statuses, labels, etc.
   A message appears if there is no data to map.
   Note the option to automatically create unmapped labels.

   

   Click the image to enlarge it.

8. Click Import.
   Your test case data imports to Zephyr Scale. The sorcerer advances to the Results stage, where import messages and errors appear.

Meet Besides

Importing Test Cases

gomezbele1980.blogspot.com

Source: https://support.smartbear.com/zephyr-scale-server/docs/test-cases/import/from-excel.html

Share this post