...
An invalid ID number will cause your import to fail. In all other instances, leave ID blank or exclude from your import CSV.
Commonly used headers for Requirements
Commonly used headers for Requirements | ||||||
Header Name | Description | Example data | Notes | |||
|---|---|---|---|---|---|---|
| Id | Enterprise Tester GUID number | {4c5d76e4-a21e-4f95-965a-a6890101a4cc} |
| |||
| Name | Name of the requirement | Fast Cash |
| |||
| Package | ||||||
| Description | ||||||
| Difficulty | ||||||
| Priority | ||||||
| Status | ||||||
| Type | ||||||
| Created By | ||||||
| Assigned to | ||||||
| ||||||
| Package | Name of the package(s) | Requirements|Cash Withdrawal|Fast Cash |
| |||
| Description | Description of the requirement | The customer should be able to simply select an amount and the money will be supplied if they have it in any of their accounts. | ||||
| Difficulty Level | Difficulty of the requirement | Low |
| |||
| Priority | Priority of the requirement | Major |
| |||
| Status | Status of the requirement | In Progress |
| |||
| Type | Type of requirement | Story |
| |||
| Created By | User who created the requirement | bloggsj | ||||
| Assigned to | User who the requirement is assigned to | smithl | ||||
| Created At | Date the requirement as created | 22/09/2016 | Created At | |||
| Last Updated At | Date the requirement was last update | 27/09/2016 | ||||
| Commonly used headers for in Test Scripts | ||
Header Name | Description | Notes |
|---|---|---|
| Id | Enterprise Tester GUID number |
|
| Name | ||
| Package | ||
| Description | ||
| Difficulty | ||
| Priority | ||
| Status | ||
| Type | ||
| Created By | ||
| Assigned to | ||
| Created At | ||
| Last Updated At | ||
...
- 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.
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.
...