Share this page

# Push test run results

This section explains when to pushes test run results to OpenText Software Delivery Management and which test run related data is pushed.

In this topic:

## When to push test run results

When a test instance under a test set is run, and when the time scheduled for the sync is due, the test run result is pushed to ALM Octane.

Back to top

## How to push test run results

When a test set is pushed to OpenText Software Delivery Management for the first time, a new test suite and test are automatically created in OpenText Software Delivery Management. In the subsequent syncs, the test suite data is updated with the test run data.

Entity mapping

OpenText Application Quality Management Entity | OpenText Software Delivery Management Entity | Notes
--- | --- | ---
Test Set | Test Suite | In 15.5.1 and later, only test sets targeted for a cycle are pushed. In 15.5, all test sets can be pushed.
Test Configuration | Automated Test | None
Test Run | Automated Run | None

Sync rules

- In the first sync

  When | What happens in OpenText Software Delivery Management
  --- | ---
  Run a test instance in a test set | A test suite is created for the test set, and a suite run is created in the test suite. An automated test is created for the test, and an automated run is created in the automated test for the test run. The automated test is added to the test suite.

- In every subsequent sync

  When | What happens in OpenText Software Delivery Management
  --- | ---
  Run an existing test instance in a synced test set. | The existing suite run in the mapped test suite is updated. A previous run is created in the mapped automated run.
  Add a synced test into a test set that's not synced. Run the test instance in the test set. | A test suite is created for the test set, and a suite run is created in the test suite. The mapped automated test is added to the test suite. A new automated run is created in the mapped automated test.
  Add a test that's not synced into a synced test set. Run the test instance in the test set. | The existing suite run in the mapped test suite is updated An automated test is created for the test, and an automated run is created in the automated test for the test run. The automated test is added to the mapped test suite.
  Cut and paste a synced test set. Run an existing test instance in the test set. | The existing suite run in the mapped test suite is updated. A previous run is created in the mapped automated run.
  Copy and paste a synced test set, or change the test set name. Run an existing test instance in the test set. | A suite run is created in the mapped test suite. An automated run is created in the mapped automated test.
  Assign a synced test set to a different release. Run an existing test instance in the test set. | If the same release does not exist in ALM Octane, the test set will not be synced. If the same release exists in ALM Octane: A suite run is created in the mapped test suite. An automated run is created in the mapped automated test.
  Cut and paste a synced test, or change the test name. Run the test instance in a synced test set. | The mapped suite run is updated. An automated test is created, and an automated run is created in the automated test. The automated test is added to the mapped test suite.
  Update the status of a synced test run. Run the test instance in the test set. | The mapped suite run is updated. A previous run is created in the mapped automated run.

Back to top

## Data mapping

The following table explains which data is pushed and how it is presented in OpenText Software Delivery Management.

OpenText Application Quality Management Data | OpenText Software Delivery Management Data | Notes
--- | --- | ---
<Test Set ID + name> | Test Suite name | For example, `32899 Dashboard display mode`
<Test Set ID + name> | Test Suite Run name | None
<Test full path in Test Plan> | Test: Package (in the Planning tab of a test suite) | For example, `Subject\Automation`
ALM/<domain name>/<project name> | Test: Component (in the Planning tab of a test suite) Component (in the Suite Runs tab of a test suite and the Runs tab of a test suite run). Available in versions: 15.5.1 and later. | For example, `ALM/DEFAULT/ALM 15.50`
Test ID | Test: External test id (in the Planning tab of a test suite) | For example, `3`
<Test Configuration ID + name> | Test: Name (in the Planning tab of a test suite) | For example, `1003 Login as a user from a non-ALM IdP`
Duration of a test run | Duration (in the Runs tab of a test) | The duration is in seconds.
Status of a test run | Status (in the Runs tab of a test) | For details about status value mapping, see Status mapping.
Exec Date + Exec Time of a test run | Started (in the Runs tab of a test) Run Started (in the Previous Runs tab of a test run) | For example, `7/21/2020 6:26:15 AM`
<Test Set ID + name> | Name (in the Runs tab of a test) | None
<TD link of a test run> | External report url (In the Runs tab of a test, and in the Previous Runs tab of a test run) | Clicking the link in the External report url field, you can open the test run.
<Test Set ID + name> | External run id (in the Suite Runs tab of a test suite) | None
Test Instance ID | External run id (in the Runs tab of a test) | If multiple test instances are added from one test configuration, the same automated test is added to the test suite for equal multiple times, differentiated by External test in suite id. The multiple runs of one test instance will all be pushed to the corresponding automated test as test runs, differentiated by External run id.
<Cycle assigned to the test set> | Milestone (in the Suite Runs tab of a test suite) | Available in versions: 15.5.1 and later If a cycle is assigned to the test set, to push the cycle information to the mapped test suite, a milestone with the same name as the cycle and a release with the same name as the cycle's release should be created in OpenText Software Delivery Management before the sync runs.
<Release of the cycle assigned to the test set> | Release (in the Suite Runs tab of a test suite) | If a release cycle is assigned to the test set in ALM, to push the cycle's release information to the mapped test suite in ALM Octane, a release with the same name should be created in ALM Octane before the sync runs. If no release cycle is assigned to the test set in ALM, in ALM 15.5.1, the test set will not be pushed to ALM Octane, and in ALM 15.5, it will be pushed to ALM Octane and the "default" release will be assigned to the mapped test suite in ALM Octane.
Type (in the Details tab of a test) | Test: Testing tool type (in the Planning tab of a test suite) | For details about test type mapping, see Configure octane-int-config.xml file.
<ALM user-defined field> | Test: Class name (in the Planning tab of a test suite) | For details about class mapping, see Configure octane-int-config.xml file.
Test Suite URL | URL of the test suite created for the test set | If auto-fix is enabled for the Test Suite URL field, the field value is updated when the URL is invalid in the format. For details, see Enable auto-fix.

Back to top

https://admhelp.microfocus.com Application Quality Management 8942
Tips to improve your search results... OpenText™ Application Quality Management Help Center OpenText™ Application Quality Management Help Center OpenText™ Application Quality Management Help 26.1 All View Local Help Center View Online Help Center Version: