Push Test Run Results to ALM Octane

This section explains when ALM pushes test run results to ALM Octane and which test run related data is pushed to ALM Octane.

When ALM pushes test run results to ALM Octane

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

Back to top

How ALM pushes test run results to ALM Octane

When a test set is pushed to ALM Octane for the first time, a new test suite and test are automatically created in ALM Octane. In the subsequent syncs, the test suite data in ALM Octane will be updated with the test run data in ALM.

ALM-ALM Octane entity mapping

ALM Entity ALM Octane Entity
Test Set Test Suite
Test Configuration Automated Test
Test Run Automated Run

Sync rules

  • In the first sync

    What you did in ALM What happens in ALM Octane
    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

    What you did in ALM What happens in ALM Octane

    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.
    1. Add a synced test into a test set that's not synced.
    2. 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.

    1. Add a test that's not synced into a synced test set.
    2. 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.
    1. Cut and paste a synced test set.
    2. 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.
    1. Copy and paste a synced test set, or change the test set name.
    2. 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.
    1. Assign a synced test set to a different release.
    2. 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.
    1. Cut and paste a synced test, or change the test name.
    2. 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.
    1. Update the status of a synced test run.
    2. 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

ALM-ALM Octane data mapping

The following table explains which data is pushed from ALM to ALM Octane and how it is presented in ALM Octane.

ALM Data ALM Octane Data Notes
<Test Set ID + name> Test Suite name For example, 32899 Dashboard display mode
<Test Set ID + name> Test Suite Run name  
<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) 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)  
<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 in ALM.
<Test Set ID + name> External run id (in the Suite Runs tab of a test suite)  
<Release of the cycle assigned to the test set folder> 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 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, 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.
ALM Octane Test Suite URL URL of the ALM Octane test suite created for the ALM test set

If auto-fix is enabled for the ALM Octane Test Suite URL field, the field value will be updated when the URL is invalid in the format.

For details, see Enable auto-fix.

Back to top