...
|
Header Name | Description | Notes | Example data | Notes |
|---|
| Id | Enterprise Tester GUID identifier | {4c5d76e4-a21e-4f95-965a-a6890101a4cc} | - “ID” is reserved for the Enterprise Tester GUID number, which should be in format {XXX-XXX-XXX-XXXX}.
- Only include “ID” header if importing data that has been exported from the same instance of Enterprise Tester and you wish to update already existing Requirements.
| {4c5d76e4-a21e-4f95-965a-a6890101a4cc} |
| Name | Name of the requirement | Fast Cash | - Requirement names must not include your file path separator “|” or “/” in the name.
| Fast Cash |
| Package | Name of the package(s) | Requirements|Cash Withdrawal|Fast Cash
Requirements is the root package of the data. - Enter the file structure that you want the data to be imported into e.g Requirements|"package name"
- If you wish to create/add further child packages you can add additional paths to the Package e.g |"package name"|"package name"
- If you are wanting to add a package directly under the Requirements root package you must include Requirements in the Package field in the CSV. e.g Requirements|"package name"|"package name"
- The pipe “|” is the default file path separator but “/” is also commonly used.
- Package names must not include your file path separator “|” or “/” in the name.
| Requirements|Cash Withdrawal|Fast Cash
Requirements is the root package of the data. |
| Description | Description of the requirement | - This should be plain text information, not HTML, markdown, richtext, etc.
| The customer should be able to select an amount
and the money will be supplied if they have it in any of their accounts. | - This should be plain text information, not HTML, markdown, richtext, etc.
|
| Difficulty Level | Difficulty of the requirementLow | - The values entered in this field should use the same values that are in the Requirement Difficulty Picklist in Enterprise Tester.
Default values are;
| Low |
| Priority | Priority of the requirement | Major | - The values entered in this field should use the same values that are in the Priority Picklist in Enterprise Tester.
Default values are;- Blocker
- Critical
- Major
- Minor
- Trivial
| Major |
| Status | Status of the requirement | In Progress | - The values entered in this field should use the same values that are in the Requirement Status Picklist in Enterprise Tester.
Default values are; - In Progress
- Review Pending
- Approved
- Requires Rework
- Rejected
- On hold
| In Progress |
| Type | Type of requirementStory | - The values entered in this field should use the same values that are in the Requirement Type Picklist in Enterprise Tester.
Default values are;
- Functional
- Non Functional
- User Interface
- Business Rule
| Story |
| Assigned to | User who the requirement is assigned to smithl | - Username has to match Enterprise Tester Username. It is not case sensitive.
| smithl |
|
| Description | Notes | Example Data |
|---|
| Id | Enterprise Tester GUID identifier | - “ID” is reserved for the Enterprise Tester GUID number, which should be in format {XXX-XXX-XXX-XXXX}.
- Only include “ID” header if importing data that has been exported from the same instance of Enterprise Tester and you wish to update already existing Test Scripts
| |
| Name | Name of the Test Script | - Test Script names must not include your file path separator “|” or “/” in the name.
- The name of the actual Test Script
| |
| Package | Name of the package(s) | - 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 |"package name"|"package name"
- If you are wanting to add a package directly under the Script Library root package you must include Script Library in the Package
- field in the CSV. e.g Script Library|"package name"|"package name"
- The pipe “|” is the default file path separator but “/” is also commonly used.
- Package names must not include your file path separator “|” or “/” in the name.
| |
| Priority | | | |
| Status | | | |
| Type | | | |
| Estimated Duration in Minutes | | - This must be entered in minutes. You cannot enter it in the format days / hours/ minutes or the import will fail.
- When the Estimated Duration in Minutes is Imported it will convert to Weeks, hours, days, minutes depending on what the Enterprise Tester Admin has set the Working Hours Per Day and Working Hours Per Week fields to for the Project.
| |
| Assigned To | | | |
| Description | | | |
| Objective | | | |
| Pre Condition | | | |
| Post Condition | | | |
| Notes | | L | |
| Step Description | | | |
| Step Expected Result | | | |
File structure / packages:
...
...
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.
- An invalid ID number will cause your import to fail. In all other instances, leave ID blank or exclude from your import CSV.
...
Start CSV Import
Select the Resources tab and double click Import.
...