|
| 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 | Priority of the test script | - 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 test script | - The values entered in this field should use the same values that are in the Status Picklist in Enterprise Tester.
Default values are;
- In Progress
- Review Pending
- Approved
- Requires Rework
- Rejected
- On hold
| |
Type | Type of test script | - The values entered in this field should use the same values that are in the Test Type Picklist in Enterprise Tester.
Default values are;
- Smoke
- Functional
- Regression
- Non-Functional
- User Acceptance
| |
Estimated Duration in Minutes | Estimated time it will take to execute the test script (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 | User who the test script is assigned to | - Username has to match Enterprise Tester Username. It is not case sensitive.
| |
Description | Description of the test script | - This should be plain text information, not HTML, markdown, richtext, etc.
| |
Objective | Objective of the test script | - This should be plain text information, not HTML, markdown, richtext, etc.
| |
Pre Condition | Pre Condition of the test script | - This should be plain text information, not HTML, markdown, richtext, etc.
| |
Post Condition | Post Condition of the test script | - This should be plain text information, not HTML, markdown, richtext, etc.
| |
Notes | Notes for the the test script | - This should be plain text information, not HTML, markdown, richtext, etc.
| |
Step DescriptionNumber | Test step number | - This can only be a whole number. You cannot enter decimal places or characters
| |
Step Description | Test step description | - This should be plain text information, not HTML, markdown, richtext, etc.
| |
Step Expected Result | Test step expected result | - This should be plain text information, not HTML, markdown, richtext, etc.
| |
Step Data | Test step data | - This should be plain text information, not HTML, markdown, richtext, etc.
| |
Step Notes | Test step notes | - This should be plain text information, not HTML, markdown, richtext, etc.
| |