Versions Compared

Key

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

...

  • Any other fields, including Custom fields can be added as columns to the CSV file and imported if required.

  • At a minimum your CSV file must contain the following fields (mandatory fields may change depending on your specific Field Configuration settings in the Admin tab):

     -  For creating Requirements and Test Scripts - Name field is required
     - For  For updating Requirements and Test Scripts - Id and Name fields are required.

...

  • ID” is reserved for the Enterprise Tester GUID number, which should be in format {XXX-XXX-XXX-XXXX}.

  • An invalid ID number will cause your import to fail. In all other instances, leave ID blank or exclude from your import CSV.

...


  •  

File structure / packages:

  • Enterprise Tester also allows you to easily import data into your specific file structure, simply set up a column in your CSV file with the header "Package".

  • For a Requirements import enter the file structure that you want the data to be imported into e.g Requirements|"package name"

  • For a Test Script import 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 Requirements|"package name"|"package name"|"package name"

  • The pipe “|” is the default file path separator but “/” is also commonly used.

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

...