Versions Compared

Key

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

...

Commonly used headers for Requirements

Header Name

Description

Example data

Notes

IdEnterprise Tester GUID numberidentifier{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.
NameName of the requirementFast Cash
  • Requirement names must not include your file path separator “|” or “/” in the name.
PackageName of the package(s)Requirements|Cash Withdrawal|Fast Cash
  • If you wish to create/add further child packages you can add additional paths to the Package 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.
DescriptionDescription of the requirementThe 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 LevelDifficulty 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;
    • High
    • Medium
    • Low
PriorityPriority of the requirementMajor
  • 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 requirementIn 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
TypeType 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
Assigned toUser who the requirement is assigned to smithl
  • Username has to match Enterprise Tester Username. It is not case sensitive.
Commonly used headers in Test Scripts

Header Name

Description

Notes

IdEnterprise Tester GUID numberidentifier
  • 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 or Test Scripts
Name  
Package  
Description  
Difficulty  
Priority  
Status  
Type  
Created By  
Assigned to  
Created At  
Last Updated At  
  

...