...
Now select the Resources tab and double click Import.
Follow the four step import wizard; starting with configuring where you would like your test scripts 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. For the example above scripts are chosen.
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. Importing to Enterprise Tester custom fields is also supported.
| Note |
|---|
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 “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 or requirements (an invalid ID number will cause your import to fail). In all other instances, leave this field blank or exclude from your import CSV. |
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 test scripts, select the Explorer tab and open the project script library you imported to. The test scripts you have imported will be displayed here.
Updating Scripts By Importing a CSV File
...