Versions Compared

Old Version 30

changes.mady.by.user Catch Admin

Saved on

compared with

New Version 31

changes.mady.by.user Catch Admin

Saved on

Key

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

...

 

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.
 
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
  
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
Type 
 
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  
  • This should be plain text information, not HTML, markdown, richtext, etc.
 
Objective  
  • This should be plain text information, not HTML, markdown, richtext, etc.
 
Pre Condition  
  • This should be plain text information, not HTML, markdown, richtext, etc.
 
Post Condition  
  • This should be plain text information, not HTML, markdown, richtext, etc.
 
Notes  
  • This should be plain text information, not HTML, markdown, richtext, etc.
 
Step Description  
  • This should be plain text information, not HTML, markdown, richtext, etc.
 
Step Expected Result  
  • This should be plain text information, not HTML, markdown, richtext, etc.
 
Step Data  
  • This should be plain text information, not HTML, markdown, richtext, etc.
 
Step Notes  
  • This should be plain text information, not HTML, markdown, richtext, etc.
 


More tips:

  • Enterprise Tester will automatically import your records in the same order they appear in the CSV file. If you wish to control the order in which records are imported, add a column to your CSV file called Order Number and number records in the order you would like them to appear.

  • Breaking entities into packages of less than 200 individual items will ensure optimal performance.

  • Field mappings must be one-to-one, two import fields cannot map to one Enterprise Tester field.

  • Some fields will prompt you for additional information pertaining to that field e.g. you will be asked to indicate if the value in the CSV file is the package name or ID.

  • You must supply the ID if you are updating fields

  • You must NOT supply the ID if you want to create new Requirements or Test Scripts.

  • If you do map the ID field then every entity must have an ID. You cannot update and create new during the same import.

  • You cannot blank out a mapping once it has been made without restarting the entire wizard.
     
  • An invalid ID number will cause your import to fail. In all other instances, leave ID blank or exclude from your import CSV.

...