Page History

• “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.
• NOTE: If you are importing data that has been exported from Enterprise Tester with the ID and you import it into a different project or package, this action will move the test script to the selected project or package

• Requirement names must not include your file path separator “|” or “/” in the name.

• 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.

• This should be plain text information, not HTML, markdown, richtext, etc.

• 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

• 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

• 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

• 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

• Username has to match Enterprise Tester Username. It is not case sensitive.

• “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
  
  
• NOTE: If you are importing data that has been exported from Enterprise Tester with the ID and you import it into a different project or package, this action will move the test script to the selected project or package

• Test Script names must not include your file path separator “|” or “/” in the name.
• The name of the actual Test Script

• 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.

• 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

• 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

• 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

• 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 Days Per Week fields to for the Project.
  The default settings in Enterprise Tester are;
  • Working Days Per Week = 5
  • Working Hours Per Day = 8

7350

This will be converted to 3 weeks, 2 hours, 30 minutes using the default Enterprise Tester settings.

• Username has to match Enterprise Tester Username. It is not case sensitive.

• This should be plain text information, not HTML, markdown, richtext, etc.

• This should be plain text information, not HTML, markdown, richtext, etc.

• This should be plain text information, not HTML, markdown, richtext, etc.

• This should be plain text information, not HTML, markdown, richtext, etc.

• This should be plain text information, not HTML, markdown, richtext, etc.

• This can only be a whole number. You cannot enter decimal places or characters

• This should be plain text information, not HTML, markdown, richtext, etc.

• This should be plain text information, not HTML, markdown, richtext, etc.

• This should be plain text information, not HTML, markdown, richtext, etc.

Type of card = Cashflow

Account Type = Savings

• This should be plain text information, not HTML, markdown, richtext, etc.