Versions Compared

Old Version 22

changes.mady.by.user Catch Admin

Saved on

compared with

New Version 23

changes.mady.by.user Catch Admin

Saved on

Key

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

A Requirement or Test Script CSV file can be either created manually or exported from other systems.

Importing Requirements or Test Scripts via a CSV file is an effective method to create entities in bulk within Enterprise Tester.

You can  import data to either Create or Update Requirements and Test Scripts.

Preparing your CSV file
 

Creating a CSV file:

...

The header is the Name of the corresponding field in Enterprise Tester.

  • Having a header row in your CSV file is recommended, as it makes the mapping process much simpler.
  • Ensure that no two columns have the same headers.

 

Commonly used headers for Requirements

Header Name

Description

Example data

Notes

IdEnterprise 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
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"|"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.		 
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 Difficulty Picklist in Enterprise Tester.

Default values are High, Medium and Low

TypeType of requirementStory
  • 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 ByUser who created the requirement bloggsj 
Assigned toUser who the requirement is assigned to smithl 
Created AtDate the requirement as created 22/09/2016 
Last Updated AtDate the requirement was last update 27/09/2016 

...