Importing Requirements

Apart from using Enterprise Tester’s REST API there are several options for importing requirements and test scripts into Enterprise Tester.

Importing Requirements from CSV

Importing requirements or test scripts from a CSV file can be an effective method of sharing requirements and test scripts with third parties or users that are unable to share a link with any external system connected to Enterprise Tester.

A requirement or script CSV file can be either created manually or exported from tools such as Enterprise Architect.

Steps to Import Requirements Using A CSV File

Select the “Resources” tab and double click “Import”.

Follow the four step import wizard; starting with configuring where you would like your requirements to import to. Use the drop down boxes to select the destination project for your data and the type of information being imported e.g. requirements or test scripts.

Browse to where your CSV file is stored and specify if the file contains a header row using the radio buttons provided, then click on “Next”.

The application will read the CSV file and ask you to map the fields in Enterprise Tester to those in your CSV. Use the drop down boxes to map the fields in your CSV file to the fields in Enterprise Tester.

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. Field mappings must be one-to-one e.g. one import field can be mapped to one (or more) ET fields. Two import fields cannot map to one ET 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, select the ‘Explorer’ tab and open the project requirements package you imported to. The requirements you have imported will be displayed here.

Click here to view import tips..

Tips

When importing, Enterprise Tester can use your CSV file to populate records into existing packages or create new ones for you. Simply add a “Packages” column to your CSV file and specify the path and name of an existing package or new package against each record in this field. Enterprise Tester will automatically save your data to the appropriate new or existing package during import.
If you wish to create/add to a child package, you can do this by including the full path in your CSV file e.g. Requirements|Functional|Display Requirements. The format depends on the character used as your file path separator. The pipe “|” is the default file path separator but the “/” is also commonly used.
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 your records in this field as you would like them to appear in Enterprise Tester.
Requirements, Test Scripts and Incidents can be exported from Enterprise Tester to a CSV file.
Breaking requirements into packages of less than 50 individual items will ensure optimal performance.
Script, Requirement and Package names must not include your file path separator in the name. By default Enterprise Tester uses the pipe “|” as the file path separator, if you’re unsure on what this is, please check with your system administrator.
Field “ID” is reserved for the Enterprise Tester GUID ID 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 Scripts, Requirements or Use Cases (an invalid ID number will cause your import to fail). In all other instances, leave this field blank or exclude from your import CSV.