Micro Focus ALM/QC

Step 1: Connect to your Repository

First, connect to your repository by following the instructions here.

You can learn more about ALM-specific configuration in our Connector Docs.

Step 2: Construct your Model

To flow test steps, you will need to add the Test Steps entity when creating your Test model.

To do this, click + Add Entity and select the Test Steps option.

A Test Steps entity will be added. On the Model Configuration screen, you will then see two panels:

1. Test Fields: In the top section, add any fields you'd like to flow on the test (or test run) artifact that are not part of its associated test steps.
2. Test Step Fields: In the bottom section, add any fields you'd like to flow that are a part of test steps. You'll see that Hub provides some Smart Fields that are test step specific to help you get started, but you can add any other desired fields by leaving the Smart Field blank.

Here is an example of a very simple Test Model with Test Steps:

You can find general details on how to create a model here.

Step 3: Create your Collection

You can find general details on how to create a collection here.

You will see a Map Test Fields sash on your collection if:

• Your model is a Model with Test Steps, and
• Your artifact is an ALM Test, ALM Test Run

The process to map test step fields is very similar to the process on the normal Field Mapping screen. Note that both relationship(s) and other field types for test steps will be mapped on this one sash.

Note: Tests and Test Steps do not require a typical relationship field mapping to link them. We've added behind-the-scenes smarts to couple them for you.

Step 4: Configure your Integration

You can find general details on how to configure an integration here.

In order to see a Test Step Flow link on the integration configuration screen, the following conditions must be met:

• Model is of type 'Model with Test Steps'
• Artifacts in both collections have test steps
• The relevant Hub connectors must support test steps (see Connector Documentation to confirm)

Clicking the link will bring you to the Test Step Flow screen, where you can click Select to choose your desired Test Step Flow style:

Due to the sequential nature of test steps, test step flow has some unique properties:

• Test steps can only flow in one direction
• The target collection’s test steps will be kept in strict synchronization with the source collection: this means that all updates, deletions, and re-ordering of test steps will be mimicked in the target collection. Since the source collection is the system of record, any test steps that exist in the target collection but not the source collection will be removed.
• If the test steps on the target artifact are changed by an end-user, they will be updated by Hub when one of the fields or ordering on the source artifact's test steps is changed.

Note: Comments and attachments are not currently supported on Test Steps.

Step 1: Connect to your Repository

First, connect to your repository by following the instructions here. 

You can learn more about ALM-specific configuration in our Connector Docs.

Step 2: Construct your Model

To flow test steps, you will need to add the Test Steps entity when creating your Test model.

To do this, click + Add Entity and select the Test Steps option.

A Test Steps entity will be added. On the Model Configuration screen, you will now see two panels:

1. Test Fields: In the top section, add any fields you'd like to flow on the test (or test run) artifact that are not part of its associated test steps.
2. Test Step Fields: In the bottom section, add any fields you'd like to flow that are a part of test steps. You'll see that Hub provides some Smart Fields that are test step specific to help you get started, but you can add any other desired fields by leaving the Smart Field blank.

Here is an example of a very simple Test Model with Test Steps:

You can find general details on how to create a model here.

Converting Model Types

Standard Models can be converted to Test Models simply by choosing Model with Test Steps in the Model Type drop down.

Models with Test Steps cannot be converted back to Standard Models, but this should not present any challenges to integration scenarios. If Test Step Flow is not enabled in the related integrations, the test step fields in the model will simply be ignored.

Step 3: Create your Collection

You can find general details on how to create a collection here.

You will see a Map Test Fields sash on your collection if:

• Your model is a Model with Test Steps, and
• Your artifact is an ALM Test, ALM Test Run, Octane Test, or Octane Manual Run

The process to map test step fields is very similar to the process on the normal Field Mapping screen. Note that both relationship(s) and other field types for test steps will be mapped on this one sash.

Note: Tests and Test Steps do not require a typical relationship field mapping to link them. We've added behind-the-scenes smarts to couple them for you.

Step 4: Configure your Integration

You can find general details on how to configure an integration here.

In order to see a Test Step Flow link on the integration configuration screen, the following conditions must be met:

• Model is of type 'Model with Test Steps'
• Artifacts in both collections have test steps
• The relevant Hub connectors must support test steps (see Connector Documentation to confirm)

Clicking the link will bring you to the Test Step Flow screen, where you can click Select to choose your desired Test Step Flow style.

Due to the sequential nature of test steps, test step flow has some unique properties:

• Test steps can only flow in one direction
• The target collection’s test steps will be kept in strict synchronization with the source collection: this means that all updates, deletions, and re-ordering of test steps will be mimicked in the target collection. Since the source collection is the system of record, any test steps that exist in the target collection but not the source collection will be removed.
• If the test steps on the target artifact are changed by an end-user, they will be updated by Hub when one of the fields or ordering on the source artifact's test steps is changed.

Note: Comments and attachments are not currently supported on test steps.

Connect to your Repositories

First, connect to your repository by following the instructions here.

You can learn more about connector-specific configuration in our Connector Docs.

Set Up your Model

Review general details on creating or reusing a model.

For this integration scenario, you will need to add the following custom fields to your model:

Test Steps

ALM

You will need to add the following custom fields to your ALM instance:

ALM Octane

You will need to add the following custom fields to your ALM Octane instance:

Create your Collections

You can learn general details on configuring collections here:

• Work Item Collection (Repository)

• Container Collection (Repository)

Review the details in the sections below to ensure that any required fields are mapped in your collections.

Configure your Integrations

You can learn general details on configuring integrations here: 

• Work Item Synchronization
• Container + Work Item Synchronization

For this integration scenario, you will need to configure the following integrations:

• ALM Requirement Folders <> ALM Octane Requirement Folders
• ALM Requirements <> ALM Octane Requirements
• ALM Test Sets -> ALM Octane Test Suites
• ALM Test Instances -> ALM Octane Tests
• ALM Test Runs <> ALM Octane Runs
• ALM Defects <> ALM Octane Defects

Review the details in the table below to ensure that your integrations are configured correctly.

Functional Limitations