Test Management for Jira plugin

The Test Management for Jira plugin provides Jira users test coverage and status information directly on native Jira epics, stories, issues, or custom types.

In this topic:

Overview

The Test Management for Jira plugin allows Jira users to continue planning and working in Jira, with immediate visibility into the quality processes being managed in OpenText Core Software Delivery Platform. This plugin helps Jira users understand test coverage and pass/fail status, while providing QA with full visibility and alignment to the development process being managed in Jira.

For details on supported Jira and OpenText Core SDP versions, see Support Matrix.

Benefits of the plugin and Connect

The Test Management for Jira plugin helps Jira users establish visibility into the quality process being managed in OpenText Core SDP. For example, you can see the test coverage of an OpenText Core SDP user story in Jira.

With Connect you can synchronize entities and issue types between OpenText Core SDP and Jira, including releases, sprints, and backlog items, but not including tests. For details, see Use-case: Syncing OpenText Core Software Delivery Platform and Jira.

If you use both Connect and the Test Management for Jira plugin, backlog items are synced from OpenText Core SDP to Jira using Connect. For those backlog items you see test coverage in Jira using the plugin.

The plugin works based on a user-defined field that is created in OpenText Core SDP that contains the Jira issue type key. This way the plugin knows where to put the test coverage details. Using Connect can make this easier by populating the OpenText Core SDP UDF with Jira key values.

Back to top

Installation

This section describes how to install the plugin.

Back to top

Configuration

You can configure multiple OpenText Core SDP spaces, and multiple workspaces in each space.

1. Create a UDF of type string containing the Jira issue key. Add this to your OpenText Core SDP features, user stories, defects, application modules, and requirement documents.

   You can do this when you synchronize Jira with OpenText Core SDP, or without synchronization. For example, if you have a user story in OpenText Core SDP to cover the quality of a user story in Jira, you can create a UDF and manually enter its Jira issue key.

2. In the plugin configuration screen > Spaces area (Shared Spaces in the Cloud version), click Create.

3. Enter a name for the space, the OpenText Core SDP URL, and the client ID and client secret used to access the space. For details, see API access.

4. In the plugin configuration screen > Workspaces area, click Create.

5. Create one or more workspace configurations as follows:

   1. Select a space from the list of spaces you defined, using the space name.

   2. Select a workspace.

      If you are using the Jira on-premises plugin, you can select multiple workspaces.

   3. Enter the OpenText Core SDP UDF in the Mapping field area (for example, jira_key_udf).

      Suggestions for relevant UDFs based on the workspace you selected are provided. These are the fields that include jira in their name.

      If you selected multiple workspaces in Jira on-premises, the Mapping field suggestions list the intersection of the relevant UDFs, meaning those that appear in all of the selected workspaces.

   4. The Entity types field is automatically populated with the OpenText Core SDP entities that have this UDF defined, to help you verify that you entered the correct Mapping field.

      If you selected multiple workspaces in Jira on-premises, this shows the intersection of all the selected workspaces.

   5. Select one or more Jira projects and Jira issue types where you want to see quality from OpenText Core SDP.

   Note: If you experience connection problems when installing a Jira on-premises environment, add a proxy.

Back to top

Test Coverage widget

After setting up the plugin, the OpenText Core Software Delivery Platform Test Coverage widget is added to issue details. The widget shows the number of tests related to the entity, and the summary of the last runs of these tests.

Each test can be run using more than one configuration, for example using different browsers. The widget shows a summary of the last run status of all the configurations. As a result, an entity might have (for example) 1 test and 3 test runs, since each run reflects a different configuration.

You can drill from the widget to the entity in OpenText Core SDP, and to its related test details.

Back to top

Data Security and Privacy Statement (On-Premises)

The Test Management for Jira plugin does not exfiltrate any of your data from the machine that hosts Jira.

The only information that the plugin stores is the configuration details listed in the Configuration section above, that specify which OpenText Core SDP space you are mapping to which Jira project. This is stored in the database management system that you have configured Jira to use.

Privacy

The OpenText Core SDP – Test Management for Jira plugin does not store any personally identifiable information in our databases.

OpenText encourages the customer to ensure secure connection between the plugin and the OpenText Core SDP server by configuring communication over HTTPS, which is not provided by OpenText. By not implementing communication over HTTPS you may be exposing the system to increased security risks. You understand and agree to assume all associated risks and hold OpenText harmless for the same. It remains at all times the Customer’s sole responsibility to assess its own regulatory and business requirements. OpenText does not represent or warrant that its products comply with any specific legal or regulatory standards applicable to Customer in conducting Customer's business.

Back to top

See also:

• Integrations
• Test Management for Jira plugin API