Receive automated test run results

Incorporate automated test results into OpenText Core Software Delivery Platform even if you do not use a CI server. When test results are received, an automated test and test run entities are created from the results. For details, see Create automated tests.

Tip: To push test results from OpenText Application Quality Management, use the OpenText Application Quality Management test run injection mechanism and not the method described below. For details, see Inject test runs from OpenText Application Quality Management.

Set up API access

For the OpenText Application Quality Management Test Results collection tool to send results to OpenText Core Software Delivery Platform, or for you to send results using the OpenText Core Software Delivery Platform UI, you must have permissions to access the server. This permission is granted with an API access key.

For details on setting up API access, see API access.

Prepare your test results

Store your automated test results in a valid XML file. Use one of the following formats:

Type	Details
A JUnit test results XML file	Use the XML schema used by JUnit tests. To relate the test results to OpenText Core Software Delivery Platform entities, add additional information about the tests (such as test type, environment details, release) in a separate configuration file or by using the command line options of the test result collection tools. For details, see the tool's readme.
An XML file using API requirements	If you have more complex cases, prepare the XML file according to the OpenText Core Software Delivery Platform test result API. For details, see Add automated test results. For an example, see Test results XML sample.

Type

Details

A JUnit test results XML file

Use the XML schema used by JUnit tests.

To relate the test results to OpenText Core Software Delivery Platform entities, add additional information about the tests (such as test type, environment details, release) in a separate configuration file or by using the command line options of the test result collection tools. For details, see the tool's readme.

An XML file using API requirements

If you have more complex cases, prepare the XML file according to the OpenText Core Software Delivery Platform test result API. For details, see Add automated test results.

For an example, see Test results XML sample.

Decide how to retrieve test results

Use one of the following methods:

Method	Details
Test Results Collection Tool	This tool sends automated test results stored in an XML file. These test results can be stored anywhere. The tool requires an OpenText Core Software Delivery Platform user name and password for authentication.
OpenText Application Quality Management Test Result Collection Tool	Retrieves the test results directly from OpenText Application Quality Management. Define filters that specify the test runs whose results you want to retrieve. The tool requires connection information for an OpenText Application Quality Management domain and project, as well as a user name and password and OpenText Core Software Delivery Platform API access. Supports 12.* versions of OpenText Application Quality Management. Send test results from OpenText Application Quality Management test types including MANUAL, OpenText Functional Testing, OpenText Functional Testing for Developers, and BPT tests.
OpenText Core Software Delivery Platform API	Use REST API calls to send test results to OpenText Core Software Delivery Platform without the test results collection tools. For details, see Add automated test results.

Method

Details

Test Results Collection Tool

This tool sends automated test results stored in an XML file. These test results can be stored anywhere.

The tool requires an OpenText Core Software Delivery Platform user name and password for authentication.

OpenText Application Quality Management Test Result Collection Tool

Retrieves the test results directly from OpenText Application Quality Management. Define filters that specify the test runs whose results you want to retrieve.

The tool requires connection information for an OpenText Application Quality Management domain and project, as well as a user name and password and OpenText Core Software Delivery Platform API access.

Supports 12.* versions of OpenText Application Quality Management. Send test results from OpenText Application Quality Management test types including MANUAL, OpenText Functional Testing, OpenText Functional Testing for Developers, and BPT tests.

OpenText Core Software Delivery Platform API

Use REST API calls to send test results to OpenText Core Software Delivery Platform without the test results collection tools.

For details, see Add automated test results.

Download a Test Result Collection tool

A Test Result Collection tool retrieves the test results and sends them to OpenText Core Software Delivery Platform.

To download a test result collection tool:

Open the Settings menu , click Spaces, and select a workspace.
Select the DevOps > CI Server tab.
Click the link to access the Test Result Collection tool or OpenText Application Quality Management Test Result Collection tool in GitHub.

Download the tool to a directory of your choice.
Unzip the downloaded file and move it to the necessary directory.

Push test results stored externally

To push test results stored outside or on an OpenText Application Quality Management server, use the command line to run the test result collection tool.

The command line options for this tool enable you to provide the necessary results, metadata, and configuration options as part of the command line or in a separate configuration file.

For details, see the readme files:

Test Results Collection tool: https://github.com/MicroFocus/octane-collection-tool
OpenText Application Quality Management Test Results Collection tool: https://github.com/MicroFocus/alm-test-result-collection-tool

Track your test results

There are a number of fields available to find your test results. Add these fields in the module grids or Dashboard graphs:

To track test results:

In the Backlog or Quality modules, add the Testing tool type column. By default, this column reports tests from the Manual Runner, Selenium, OpenText Functional Testing, OpenText Functional Testing for Developers, OpenText Core Performance Engineering, SoapUI, Protractor, and OpenText Enterprise Performance Engineering.

Filter or sort the grid accordingly to see results from these testing tools.
In Dashboard grids, filter by the Testing tool type attribute. The graph is sorted to display tests with each testing tool type.
For tests pushed from OpenText Application Quality Management, use the Component, Package, and Class Name columns in the Backlog and Quality modules. These columns are marked accordingly to identify the test results origin from OpenText Application Quality Management.

In addition, an identifier is added to the test name to show it originated in OpenText Application Quality Management.
After the test results have been retrieved, set up test assignment rules to assign the results to the relevant application modules and users. For details, see Test assignment rules.