...
|
Header Name | Description | 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.
|
| Name | Name of the requirement | Fast Cash | - Requirement names must not include your file path separator “|” or “/” in the name.
|
| Package | Name of the package(s) | Requirements|Cash Withdrawal|Fast Cash
Requirements is the root package of the data. | - 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.
|
| Description | Description of the requirement | 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 requirement | Low | - The values entered in this field should use the same values that are in the Requirement Difficulty Picklist in Enterprise Tester.
Default values are;
|
| 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
|
| 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
|
| Type | Type of requirement | Story | - 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
|
| Assigned to | User who the requirement is assigned to | smithl | - Username has to match Enterprise Tester Username. It is not case sensitive.
|
|
| Description | Notes |
|---|
| 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 | |
| Package | Package | |
| Priority | | |
| DescriptionStatus | | |
| Type | Difficulty | |
| 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 ToPriority | | |
| Status | | |
| Type | | |
| Created By | | |
| Assigned to | | |
| Created At | | |
| Last Updated AtL | | |
| | |
File structure / packages:
...