Overview

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

This allows Jira users to continue planning and working in Jira, with immediate visibility into the quality processes being managed in ALM Octane. 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.

Supported platforms:

Supported ALM Octane versions: CP10 and later

Configuration

You can configure multiple ALM Octane spaces, and multiple workspaces in each space.

  1. Create a UDF of type string in your ALM Octane features, user stories, and defects, containing the Jira issue key.

    You can do this when you synchronize Jira with ALM Octane, or without synchronization. For example, if you have a user story in ALM Octane 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, click Create.

  3. Enter a name for the space, the ALM Octane URL, and the client ID and client secret used to access the space. For details, see here.

  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.

    3. Enter the ALM Octane UDF in the Mapping field area (for example, jira_key_udf).

      The icon next to the Mapping field area provides suggestions for relevant UDFs based on the workspace you selected. These are the fields that include jira in their name.

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

    5. Select one or more Jira projects and Jira issue types where you want to see quality from ALM Octane. Each Jira project can be mapped to one workspace only.

    Note: If you experience connection problems, add a proxy in the upper right corner of the screen.

    You can edit a workspace configuration using the ellipses (…) at the right of the workspace configuration table.

ALM Octane Test Coverage Widget Summary

After setting up the plugin, the ALM Octane 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 executed 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 ALM Octane, and to its related test details.

Data Security and Privacy Statement

The ALM Octane – 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 ALM Octane 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 ALM Octane – Test Management for Jira plugin does not store any personally identifiable information in our databases.

Micro Focus encourages the customer to ensure secure connection between the plugin and the ALM Octane server by configuring communication over HTTPS, which is not provided by Micro Focus. 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 Micro Focus harmless for the same. It remains at all times the Customer’s sole responsibility to assess its own regulatory and business requirements. Micro Focus does not represent or warrant that its products comply with any specific legal or regulatory standards applicable to Customer in conducting Customer's business.


Legal Notices

Disclaimer

Certain versions of software and/or documents (“Material”) accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company.  As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company.  Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.

Warranty

The only warranties for products and services of Micro Focus and its affiliates and licensors (“Micro Focus”) are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Micro Focus shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice.

Restricted Rights Legend

Contains Confidential Information. Except as specifically indicated otherwise, a valid license is required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

Comodo Code Signing Certificate

The code signing certificate for ALM Octane was changed from Verisign to Comodo starting on January 1, 2017.

If you are installing this product on a computer with an older version of Windows, or on a computer without automatic Windows updates, the Comodo root certificate may not automatically be included as a trusted root certificate.

In such cases, we recommend manually configuring Comodo as a trusted root certificate.

For more details, see: https://technet.microsoft.com/en-gb/library/dn265983.aspx.

Copyright Notice

© Copyright 2016-2020 Micro Focus or one of its affiliates


Send documentation feedback