Page History

Tips

1. 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” 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.
2. 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.
3. 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” Order Number and number your records in this field as you would like them to appear in Enterprise Tester.
4. Requirements, Test Scripts and Incidents can be exported from Enterprise Tester to a CSV file.
5. Breaking requirements into packages of less than 50 individual items will ensure optimal performance.
6. 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. 
7. 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.