A Requirement or Test Script, character separated values (CSV) file can be either created manually or exported from other systems.

Importing Requirements or Test Scripts via a CSV file is an effective method to create entities in bulk within Enterprise Tester.

You can  import data to either Create or Update Requirements and Test Scripts.

Preparing your CSV file
 Creating a CSV file:

  • If this is the first time you are importing a CSV file into Enterprise Tester , the easiest way to do this is to Export - (see Export Data) a Requirement or Test Script first.
    This will give you a template with the correct format, including headers that you can modify and import.
  • Any other fields, including Custom fields can be added as columns to the CSV file and imported if required.

  • At a minimum your CSV file must contain the following fields (mandatory fields may change depending on your specific Field Configuration settings in the Admin tab):

     -  For creating Requirements and Test Scripts - Name field is required
     -  For updating Requirements and Test Scripts - Id and Name fields are required.

Headers:

The header is the Name of the corresponding field in Enterprise Tester.

  • Having a header row in your CSV file is recommended, as it makes the mapping process much simpler.
  • Ensure that no two columns have the same headers.

Commonly used headers for Requirements

Header Name

Description

Notes

Example data
IdEnterprise Tester GUID identifier
  • “ID” is reserved for the Enterprise Tester GUID number, which should be in format {XXX-XXX-XXX-XXXX}.
  • Only include “ID” header if importing data that has been exported from the same instance of Enterprise Tester and you wish to update already existing Requirements.
  • NOTE: If you are importing data that has been exported from Enterprise Tester with the ID and you import it into a different project or package, this action will move the test script to the selected project or package
{4c5d76e4-a21e-4f95-965a-a6890101a4cc}
NameName of the requirement
  • Requirement names must not include your file path separator “|” or “/” in the name.
Fast Cash
PackageName of the package(s)
  • Enter the file structure that you want the data to be imported into e.g Requirements|"package name"
  • If you wish to create/add further child packages you can add additional paths to the Package e.g |"package name"|"package name"
  • If you are wanting to add a package directly under the Requirements root package you must include Requirements in the Package field in the CSV. e.g Requirements|"package name"|"package name"
  • The pipe “|” is the default file path separator but “/” is also commonly used.
  • Package names must not include your file path separator “|” or “/” in the name.
Requirements|Cash Withdrawal|Fast Cash

Requirements is the root package of the data. 
DescriptionDescription of the requirement
  • This should be plain text information, not HTML, markdown, richtext, etc.
The customer should be able to select an amount
and the money will be supplied if they have it in any of their accounts.
Difficulty LevelDifficulty of the requirement
  • The values entered in this field should use the same values that are in the Requirement Difficulty Picklist in Enterprise Tester.

    Default values are;
    • High
    • Medium
    • Low
Low
PriorityPriority of the requirement
  • The values entered in this field should use the same values that are in the Priority Picklist in Enterprise Tester.

    Default values are;
    • Blocker
    • Critical
    • Major
    • Minor
    • Trivial
Major
StatusStatus of the requirement
  • The values entered in this field should use the same values that are in the Requirement Status Picklist in Enterprise Tester.

    Default values are; 
    • In Progress
    • Review Pending
    • Approved
    • Requires Rework
    • Rejected
    • On hold
In Progress
TypeType of requirement
  • The values entered in this field should use the same values that are in the Requirement Type Picklist in Enterprise Tester.

    Default values are;
    • Functional
    • Non Functional
    • User Interface
    • Business Rule
Story
Assigned toUser who the requirement is assigned to
  • Username has to match Enterprise Tester Username. It is not case sensitive.
smithl

Commonly used headers in Test Scripts

Header Name

Description

Notes

Example Data
IdEnterprise Tester GUID identifier
  • “ID” is reserved for the Enterprise Tester GUID number, which should be in format {XXX-XXX-XXX-XXXX}.
  • Only include “ID” header if importing data that has been exported from the same instance of Enterprise Tester and you wish to update already existing Test Scripts

  • NOTE: If you are importing data that has been exported from Enterprise Tester with the ID and you import it into a different project or package, this action will move the test script to the selected project or package
{f9778744-1914-4e37-847e-a6890101fb68}
NameName of the Test Script
  • Test Script names must not include your file path separator “|” or “/” in the name.
  • The name of the actual Test Script
Customer Validated
PackageName of the package(s)
  • Enter the file structure that you want the data to be imported into e.g Script Library|"package name"
  • If you wish to create/add further child packages you can add additional paths to the Package e.g |"package name"|"package name"
  • If you are wanting to add a package directly under the Script Library root package you must include Script Library in the Package field in the CSV. e.g Script Library|"package name"|"package name"
  • The pipe “|” is the default file path separator but “/” is also commonly used.
  • Package names must not include your file path separator “|” or “/” in the name.
Script Library|Access ATM
PriorityPriority of the test script
  • The values entered in this field should use the same values that are in the Priority Picklist in Enterprise Tester.

    Default values are;
    • Blocker
    • Critical
    • Major
    • Minor
    • Trivial
Major
StatusStatus of the test script
  • The values entered in this field should use the same values that are in the Status Picklist in Enterprise Tester.

    Default values are; 
    • In Progress
    • Review Pending
    • Approved
    • Requires Rework
    • Rejected
    • On hold
In Progress
TypeType of test script
  • The values entered in this field should use the same values that are in the Test Type Picklist in Enterprise Tester.

    Default values are;
  • Smoke
  • Functional
  • Regression
  • Non-Functional
  • User Acceptance
Functional
Estimated Duration in MinutesEstimated time it will take to execute the test script (in minutes)
  • This must be entered in minutes. You cannot enter it in the format days / hours/ minutes or the import will fail.
  • When the Estimated Duration in Minutes is Imported it will convert to Weeks, hours, days, minutes depending on what the Enterprise Tester Admin has set the Working Hours Per Day and Working Days Per Week fields to for the Project.
    The default settings in Enterprise Tester are;
    • Working Days Per Week = 5
    • Working Hours Per Day = 8

7350

This will be converted to 3 weeks, 2 hours, 30 minutes using the default Enterprise Tester settings.

Assigned ToUser who the test script is assigned to
  • Username has to match Enterprise Tester Username. It is not case sensitive.
Smithl
DescriptionDescription of the test script
  • This should be plain text information, not HTML, markdown, richtext, etc.
This is where the card and pin are correct as the customer is given access to the ATM
ObjectiveObjective of the test script
  • This should be plain text information, not HTML, markdown, richtext, etc.
Customer can access ATM using card with correct pin number
Pre ConditionPre Condition of the test script
  • This should be plain text information, not HTML, markdown, richtext, etc.
Card has pin already loaded
Post ConditionPost Condition of the test script
  • This should be plain text information, not HTML, markdown, richtext, etc.
Card is returned to customer
NotesNotes for the the test script
  • This should be plain text information, not HTML, markdown, richtext, etc.
The goal of the Customer is to access the ATM so that they can complete a transaction
Step NumberTest step number
  • This can only be a whole number. You cannot enter decimal places or characters
1
Step DescriptionTest step description
  • This should be plain text information, not HTML, markdown, richtext, etc.
Customer inserts card into ATM
Step Expected ResultTest step expected result
  • This should be plain text information, not HTML, markdown, richtext, etc.
ATM Accepts Card
Step DataTest step data
  • This should be plain text information, not HTML, markdown, richtext, etc.

Type of card = Cashflow

Account Type = Savings

Step NotesTest step notes
  • This should be plain text information, not HTML, markdown, richtext, etc.
Ensure Card is of type cashflow, not debit or credit card


More tips:

  • Enterprise Tester will automatically import your records in the same order they appear in the CSV file. If you wish to control the order in which records are imported, add a column to your CSV file called Order Number and number records in the order you would like them to appear.

  • Breaking entities into packages of less than 200 individual items will ensure optimal performance.

  • Field mappings must be one-to-one, two import fields cannot map to one Enterprise Tester field.

  • Some fields will prompt you for additional information pertaining to that field e.g. you will be asked to indicate if the value in the CSV file is the package name or ID.

  • You must supply the ID if you are updating fields

  • You must NOT supply the ID if you want to create new Requirements or Test Scripts.

  • If you do map the ID field then every entity must have an ID. You cannot update and create new during the same import.

  • You cannot blank out a mapping once it has been made without restarting the entire wizard.
     
  • An invalid ID number will cause your import to fail. In all other instances, leave ID blank or exclude from your import CSV.
  •  If you are importing data that has been exported from Enterprise Tester with the ID and you import it into a different project or package, this action will move the test script to the selected project or package


Start CSV Import 

Select the Resources tab and double click Import.


Select the Project you would like to import your data to and the Type of data to be imported (Requirements or Test Scripts).

Browse to your CSV file and specify if the file contains a header row, then click on Next.

The application will read the CSV file and the Data Mapping screen will be displayed.

  • The "Save mapping as a template?" check box will allow you to save and reuse the mappings.   Add a Template Name when this is ticked.
  • The Import File (on the left hand side) displays the columns (headers) from the file that you are importing.
  • The Enterprise Tester Field  (on the right hand side) lets you select fields from Enterprise Tester.


You can automatically map the Import File fields to the Enterprise Tester field by selecting the Automap? checkbox.
This will automatically map most of the fields. Note: Some fields will still need to be added Manually as they have various options to select from.



To map the fields manually use the drop down boxes to map the Import File fields to the Enterprise Tester Field.


Once the fields have been mapped, click on Next at the bottom of the page, followed by Yes to begin importing.

When the import is complete the following status window will appear.  If there have been errors, click on the click here to view the error log link for information on why the export failed. If the export was successful, click Cancel. 

To view the imported Requirements or Test Scripts, select the Explorer tab and open the relevant folder.


Re-using Saved Templates

When you have previously saved mappings as a template, you can re-use these as follows:

  • Select your CSV file as per the usual process
  • Highlight the required mapping template
  • Click the Next button 

The mappings will be automatically loaded.


Update Data By Importing a CSV File

Updating Requirements or Test Scripts by importing a CSV file is similar to creating new data. Some additional points to note are:

  1. A unique ID or GUID is required in the CSV file so Enterprise Tester can match the records that need to be updated.
  2. To obtain the ID or GUID, perform an export of the records you want to update and include the ID column in the export.
  3. When importing the data make sure the ID and any fields that need updating are included in the CSV file.
  • No labels