Connecting to External Systems
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.
Enterprise Tester interfaces with the following:
External System | Requirements / User Stories | Test Cases / Use Cases | Incidents / Defects |
---|---|---|---|
Enterprise Architect (Sparx Systems) | Yes | Yes | No |
JIRA (Atlassian) | Yes | No | Yes |
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.
Add an External System
To add a connection to an external system, you will need to have Administration permissions for Enterprise Tester.
- Open the Admin tab of the tree view, click on Extensions and double click External Systems.
- From the External Systems summary screen, you can view all existing connections and their enabled and configuration status.
- Click Add from the toolbar and add a name for your external system connection, select a Connection Type
- The configuration screen of the external system type you chose will appear:
Enterprise Architect
Connection Type | Select the EA repository type from the drop down list. |
Connection String | 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. |
JIRA
Name | Enter a name for the external system that will identify it within Enterprise Tester. |
Enabled | Check this box to enable the connection to the external system. |
Application Url: | 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. |
UserName | Enter a Gateway Account* username for the external system. |
Password | Enter the password for the gateway username. |
Ignore Remote | Check this box to ignore invalid remote certificates. |
Important Information
* The Gateway Account requires the following permissions in each Jira Project you wish to synchronise with Enterprise Tester
For one-way synchronisation from JIRA to ET:
Browse Projects
View Read-Only Workflow
For one-way synchronisation from ET to JIRA or bi-directional synchronisation:
Browse Projects
View Read-Only Workflow
Assign Issues
Close Issues
Create Issues
Edit Issues
Link Issues
Modify Reporter
Resolve Issues
Schedule Issues
Transition Issues
Add Comments
Edit Own Comments
Create Attachments
- The next step is to set up your links between Enterprise Tester and external systems at a project level - known as Project Links in Enterprise Tester.
- Here are details on how to set up Project Links for each external system:
Synchronizing Requirements with JIRA
Synchronizing Incidents with JIRA