Child pages
  • Importing Data
Skip to end of metadata
Go to start of metadata

There are several options for importing data into Enterprise Tester:

  • Import via CSV
  • Import via External Systems
  • Import via Enterprise Tester API

Import via CSV

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

A Requirement or Test Script CSV file can be either created manually or exported from other systems.


Preparing your CSV file

At minimum, Enterprise Tester requires your CSV file to contain the following fields (mandatory fields may change depending on your specific Field Configuration settings in the Admin Tab):

  • Requirements Import - Name
  • Test Script Import - Name, Step Description, Step Expected Result


To import more than one Test Script, or multiple Steps, format the CSV file as per the below example which contains two Test Scripts with three Steps each.  

Any other fields, including Custom fields can be added as columns to the CSV file and imported if required.


CSV Preparation Tips

  • Having a header row in your CSV file is a good idea, the mapping process is much easier.

  • Ensure that no two columns have the same heading.

  • Enterprise Tester also allows you to easily import data into your specific file structure, simply set up a column in your CSV file with the header Package.

  • For a Requirements import enter the file structure that you want the data to be imported into e.g Requirements|"package name"

  • For a Test Script import 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 Requirements|"package name"|"package name"|"package name"

  • The pipe “|” is the default file path separator but “/” is also commonly used.

  • Script, Requirement and Package names must not include your file path separator “|” or “/” in the name.

  • 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.

  • Field “ID” is reserved for the Enterprise Tester GUID number, which should be in format {XXX-XXX-XXX-XXXX}.

  • Only include “ID” if importing data that has been exported from the same instance of Enterprise Tester and you wish to update already existing Requirements or Test Scripts

  • An invalid ID number will cause your import to fail. In all other instances, leave ID blank or exclude from your import CSV.

  • 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.



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, use the drop down boxes to map the Import File fields to the fields in Enterprise Tester. 

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.


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.


Importing Data from External Systems

Creating a link between the two applications can be used to regularly update Requirements, Test Scripts and Incidents.  

Refer here for more information on how to create a links between Enterprise Tester and External Systems.



Importing Data via the API

The Enterprise Tester Rest API is extensive and can be used to perform the majority of functions available in the user interface.

Refer here for more details on our API.



  • No labels