Uploading Test Cases From Excel to Jira

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

Import from Excel is non supported in Zephyr Scale 7.2 and later. We'd suggest saving your Excel canvass to a CSV file and importing examination cases from this file. See Import Test Cases From CSV for details. The data below about importing from Excel sheets applies to earlier Zephyr Scale versions.

Yous can import Excel files (.xlsx) directly into Zephyr Scale using a sorcerer.

If your data is in the Numbers spreadsheet program on a Mac Bone, no worries! Just export to XLS earlier y'all proceed with the import process.

This topic is split up into ii main parts:

Note:

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

Before you import: format your Excel spreadsheet

To import and allow you to map your fields and data accurately, the Excel spreadsheet you lot use to import your examination-instance information needs to bide by a few formatting specifications.

Define your test steps

There are two means you tin format your test steps. Choose one.

Option 1

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

Click the image to enlarge it.

Pick 2

You lot tin import the script blazon (Plain Text) by creating a cavalcade for Exam Script Plain Text, as demonstrated in the following example:

Import limitations

A few limitations to keep in mind:

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

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

• Excel time cells volition non import and must manually exist inverse to text format.

System fields available for import

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

System Field	Description
Name	Text field, single line. The Proper name field is required. Example: Validate mandatory fields.
Precondition	Text field, multi-line. May contain line breaks. Example: Leaves fields in blank to verify if a user can accelerate without filling mandatory fields.
Objective	Text field, multi-line. Can contain line breaks. Example: Ensure the user is unable to proceed without filling mandatory fields.
Test Script (Steps) - Pace	Text field, multi-line. Tin contain line breaks. Should non exist used if the Test Script (Patently Text) field has been mapped. Instance: Exit username field blank and attempt to proceed further.
Exam Script (Steps) - Expected Upshot	Text field, multi-line. Can contain line breaks. Should not be used if the Exam Script (Manifestly Text) field has been mapped. Example: User is unable to go on further. The page warns well-nigh a mandatory field.
Exam Script (Apparently Text)	Text field, single line. Should non be used if whatsoever Test Script (Steps) field has been mapped. Example: The content of the error bulletin should be "field user proper noun is mandatory."
Binder	Folder structure separated by a slash (/). Example: "binder 1/folder two" 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 exist merged.
Status	Proper noun or brusque sentence describing the value. A value-mapping step will exist available for such fields. Example: Typhoon, Approved, In Review, etc.
Priority	Proper name or brusk sentence describing the value. A value-mapping stride will exist available for such fields. Case: Low, Medium, High, etc.
Component	Name or short sentence describing the value. A value-mapping stride volition exist available for such fields. The component field is the aforementioned component used past the Jira project. Example: Manufacturing
Labels	Name or short judgement describing the value. A value-mapping step will be available for such fields. Example: Functional, Non-Functional, Smoke, Integration, etc.
Owner	The key of existing Jira users. If the user doesn't exist, it will not be imported and a warning will be generated. Example: ccaetano, jbond, etc.
Estimated Time	The estimated time in seconds or using format hh:mm. If the value can't exist parsed, information technology will not be imported and a alarm will be generated. Example: 00:40 or only 2400 (seconds)
Coverage	An issue key list separated past a comma. If an consequence doesn't exist for a given primal, it volition non be imported and a alert volition exist generated. Example: TIS-490, WOR-356, etc.

Importing your information to Zephyr Scale

1. Open up the projection you want to import the examination cases into, click Tests > Ellipses > Import from File.

   

   Click the image to enlarge it.

   The Import from File wizard 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 divers area or by clicking Choose the File and selecting information technology from your local storage.
   Your file uploads to the wizard.

4. Complete the fields in the Settings section.

   • Destination Folder - The folder into which yous desire to import your exam cases. If a binder for your file does not be in Zephyr Calibration, one will be created during the import process.
     

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

   • Start Import at Row - The row in which yous want the import to begin.

     Annotation:

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

5. Click Next.

   

   Click the epitome to enlarge it.

   The wizard progresses to the Field Mapping stage.

6. Map your fields, then click Adjacent.
   Unmapped fields will non be created.

   

   Click the image to enlarge it.

   The magician progresses to the Data Mapping stage.

7. Map your information type for components, priorities, statuses, labels, etc.
   A message appears if at that place 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 information imports to Zephyr Calibration. The wizard advances to the Results phase, where import messages and errors appear.

See Likewise

Importing Exam Cases

lopezthistagating.blogspot.com

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

Share this post