Page History

...

Header Name	Description	Example data	Notes
Commonly used headers for Requirements
Id	Enterprise Tester GUID number	{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 or Test Scripts
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	If you wish to create/add further child packages you can add additional paths to the Package e.g Requirements\|"package name"\|"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.
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; High Medium 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
Status	Status of the requirement	In Progress	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 and Low
Type	Type of requirement	Story	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 and Low
Created By	User who created the requirement	bloggsj
Assigned to	User who the requirement is assigned to	smithl
Created At	Date the requirement as created	22/09/2016
Last Updated At	Date the requirement was last update	27/09/2016	Username has to match Enterprise Tester exactly.

Header Name	Description	Notes
Commonly used headers in Test Scripts
Id	Enterprise Tester GUID number	“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

...

Page tree

Versions Compared

Old Version 23

New Version 24

Key

Commonly used headers for Requirements

Header Name

Description

Notes