Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Commonly used headers for Requirements

Header Name

Description

Notes

Example data
IdEnterprise 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 Requirements.
{4c5d76e4-a21e-4f95-965a-a6890101a4cc}
NameName of the requirement
  • Requirement names must not include your file path separator “|” or “/” in the name.
Fast Cash
PackageName of the package(s)
  • 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. 
DescriptionDescription 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.
Difficulty LevelDifficulty of the requirement
  • The values entered in this field should use the same values that are in the Requirement Difficulty Picklist in Enterprise Tester.

    Default values are;
    • High
    • Medium
    • Low
Low
PriorityPriority of the requirement
  • 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
StatusStatus of the requirement
  • 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
TypeType of requirement
  • 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 toUser who the requirement is assigned to
  • Username has to match Enterprise Tester Username. It is not case sensitive.
smithl

Commonly used headers in Test Scripts

Header Name

Description

Notes

Example Data
IdEnterprise 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
 
NameName 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
 
PackageName 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.
 
PriorityPriority 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
 
StatusStatus 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
 
TypeType 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 MinutesEstimated 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 ToUser 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 DescriptionNumberTest step number
  • This can only be a whole number. You cannot enter decimal places or characters
 
Step DescriptionTest 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.
 

...