Apart from using Enterprise Tester’s REST API there There are several options for importing requirements and test scripts data into Enterprise Tester.
...
:
- Import via CSV
- Import via External Systems
- Import via Enterprise Tester API
Import via CSV
Importing requirements or test scripts from Requirements or Test Scripts via a CSV file can be is an effective method of sharing requirements and test scripts with third parties or users that are unable to share a link with any external system connected to to create entities in bulk within Enterprise Tester.
A requirement Requirement or script Test Script CSV file can be either created manually or exported from tools such as Enterprise Architect.
...
other systems.
Preparing your CSV file
At minimum, Enterprise Tester requires your CSV file to contain the following fields:
- Requirements Import - Name
- Test Script Import - Name, Step Description, Step Expected Result
Mandatory fields may change depending on the Field Configuration settings in the Admin Tab.
Having a header row in your CSV file is a good idea, the mapping process is much easier.
Ensure that no two columns have the same heading.
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 each Requirement enter the pathway: Requirements|package name.
- For each Test Script enter the pathway: Script Library|package name.
Importing Many Steps for a Single Test Script:
When importing many steps for a single test script, for the rows containing step 2 and above, simply leave all fields blank except for the Step Description and Expected Result. These must be complete. If you have a field for step number, Enterprise Tester will place the steps in the order you have indicated otherwise Enterprise Tester will list the test steps by order of appearance. See rows 8 and 9 in the screenshot above. Row 9 is an example of how to format an additional step in your script. In this example, the details in row 9 will import as the second step of the script in row 8.
Start CSV Import
Select the Resources tab and double click Import.
Follow the four step import wizard; starting with configuring where Select the Project you would like your requirements to import to. Use the drop down boxes to select the destination project for your data to and the type of information being imported e.g. requirements or test scripts Type of data to be imported (Requirements or Test Scripts).
Browse to where your CSV file is stored and specify if the file contains a header row using the radio buttons provided, then click on Next.
The application will read the CSV file and ask you to map the fields in Enterprise Tester to those in your CSV. Use , use the drop down boxes to map the Import File fields in your CSV file to the fields in Enterprise Tester.
Note | ||
---|---|---|
| ||
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. Field mappings must be one-to-one e.g. one import field can be mapped to one (or more) ET fields. Two import fields cannot map to one ET field. |
Once the fields have been mapped, click on ‘Next’ at Next at the bottom of the page, followed by Yes to begin importing.
When the import is complete the following status window will appear. If there have been errors, click on the click here to view the error log link for information on why the export failed. If the export was successful, click Cancel.
To view the imported requirementsRequirements or Test Scripts, select the Explorer tab and open the project requirements package you imported to. The requirements you have imported will be displayed here.relevant folder
Info | ||
---|---|---|
| ||
Additional | ||
Expand | ||
| ||
Tips
|
...
Updating Data By Importing a CSV File
Updating scripts by importing a CSV file is similar to creating new scripts. Some additional points to note are:
- You must include the script's unique ID. The script ID or GUID is a unique identifier that will allow Enterprise Tester to match the update in the CSV back to the existing script. When exporting scripts from Enterprise Tester, ensure that you include the Id field. You should always retain this in the CSV if you are importing updates.
- At a minimum, the following fields must be included in the CSV file:
- Id
- Name
- Step Data
- Step Description
- Step Expected Result
- Step Notes
- Step Number
Don't forget to also map the fields you wish to import changes for.
Importing Data from External Systems
Creating a link between the two applications can be used to regularly update Requirements, Test Scripts and Incidents.
Refer here for is the quickest and easiest method for regularly updating requirements and use cases and for synchronizing changes to requirements. Refer to the following topics for more information on how to create a project link for requirement synchronization between ET and external systems such as Enterprise Architect, JIRA, Rally, TFS.links between Enterprise Tester and External Systems.
Importing Data via the API