The ability to interface with multiple external systems is a key feature of Enterprise Tester.
Requirements, Test Scripts or Incidents (depending on which tool you are integrating with) can be synchronized between Enterprise Tester and the external system.
TFS and Rally integration with Enterprise Tester is no longer supported.
They will both be deprecated in the next Release.
Enterprise Tester interfaces with the following:
|External System||Requirements / User Stories||Test Cases / Use Cases||Incidents / Defects|
|Enterprise Architect (Sparx Systems)||Yes||Yes||No|
Once a Requirement or Incident is synchronized, Enterprise Tester adds a reference to the external ticket ID on the incident. This is visible as a hyperlink on the Entity or in the External Identifiers column of the grid.
To add a connection to an external system, you will need to have Administration permissions for Enterprise Tester.
Select the EA repository type from the drop down list.
The connection string details are dependent on the connection type. See the Enterprise Architect help topic for more information.
|Disable Import Feature|
This feature disables the ability to import from EA.
It can be useful if you would like to enable the feature for an import and then disable them after the process is complete to limit other users from initiating the process.
When disabled, the Import button is no longer available on the project link screen.
|Disable Update EA Feature|
This feature disables the ability to update EA with changes made in Enterprise Tester.
As the update feature will update all values in EA regardless of which system holds the latest change, this feature can give you some control over when updates are made.
When disabled the Update EA button is no longer available on the requirements type project link screen.
Enterprise Tester does not support updating EA Use Cases so the use case type project link screen will be unaffected.
Enter a name for the external system that will identify it within Enterprise Tester.
Check this box to enable the connection to the external system.
Enter the URL path for the external system. The URL should take the following forms:
JIRA: example https://jira.companyname.com/
|Display Url:||This URL is used when displaying links to the external system. When creating the external system, you may use a URL that is not accessible to other users, such as an internal IP address. If so, you can change the display URL to the address your users would normally use to access the other system. If no Display URL is entered the Application URL is used.|
Enter a Gateway Account* username for the external system.
Enter the password for the gateway username.
Check this box to ignore invalid remote certificates.
* The Gateway Account should be set up as an administration account in JIRA/TFS. This will allow creation and update of incidents across all projects and will hold sufficient privileges to support enhanced functionality when further integration features are implemented.
Gateway Account must be assigned to the JIRA Administrators, Developers and Users default groups in JIRA.
This will allow creation, and update of incidents across all projects and will hold sufficient privileges to support enhanced integration functionality.
Synchronizing Requirements with JIRA
Synchronizing Incidents with JIRA
Advanced settings only apply to JIRA connections.
Advanced settings allow you to configure which custom fields will be synchronized with Enterprise Tester from your External System. By default, all the custom fields are selected.
To access the Advanced Settings screen, from the Edit External Systems screen select the Advanced Settings button on the bottom right corner of the screen.
In Advanced Settings, select the custom fields to synchronize by ticking or un-ticking the check boxes.
Once you have updated the custom field synchronization configuration click Save & Close button.
Refresh Lookups will also need to be performed after adding custom fields to the synchronization configuration.