Share this page

# Run OpenText Functional Testing tests from OpenText Software Delivery Management

You can send OpenText Functional Testing tests and test results to OpenText Software Delivery Management. You can also trigger automated chain runs of the tests from OpenText Software Delivery Management.

In this topic:

## Guidelines

This integration enables you to run OpenText Functional Testing tests in PulseUno by triggering them from an OpenText Software Delivery Management test suite.

Using PulseUno chains, you can do the following:

1. Run OpenText Functional Testing tests and publish tests results to OpenText Software Delivery Management.

2. Continuously inform OpenText Software Delivery Management about any new OpenText Functional Testing tests in your PulseUno workspace.

3. You can then trigger these tests individually or as a pipeline from an OpenText Software Delivery Management test suite.

Guidelines and behaviors:

- Create an OpenText Functional Testing test runner chain that integrates with an OpenText Software Delivery Management pipeline. This chain runs a set of these tests in PulseUno and pushes results to OpenText Software Delivery Management.

  After the results are published, add the tests to an OpenText Software Delivery Management test suite so that you can run them from there. You can trigger the full pipeline but not specific tests.

- To discover new OpenText Functional Testing tests, create a chain that scans your workspace, detects these tests, and informs OpenText Software Delivery Management about them.

  After the chain runs, the discovered tests become available in OpenText Software Delivery Management. You can then trigger specific tests rather than the full pipeline from an OpenText Software Delivery Management test suite. For example, if a particular test in the pipeline fails, you can rerun only the failed test. Or you can run tests in a specific area if your test plan requires it.

  Using this chain, you no longer need to periodically run the OpenText Functional Testing test runner chain in to create new test entities in OpenText Software Delivery Management.

- If you remove a discovered OpenText Functional Testing test in your source code repository, you must manually delete it in OpenText Software Delivery Management to prevent errors.

Back to top

## Integration steps

To run chains of OpenText Functional Testing tests from OpenText Software Delivery Management, complete the following steps.

Step | Description
--- | ---
Step 1 | In PulseUno: Connect to an OpenText Software Delivery Management instance. See Connect to OpenText Software Delivery Management.
Step 2 | In PulseUno: Enable the relevant product or Git repository to use the OpenText Software Delivery Management connection. See Enable OpenText Software Delivery Management connection.
Step 3 | In PulseUno: To publish results to an OpenText Software Delivery Management pipeline, create a OpenText Functional Testing test runner chain that has the following plugin steps: The OpenText Functional Testing step. See UFT One. The Publish results to OpenText Software Delivery Management step. See Create a chain to publish to OpenText Software Delivery Management. Make sure to add the testsToRun variable on the chain. OpenText Software Delivery Management uses the testsToRun parameter to send the chain a list of tests to run. For details on how to define variables, see Add chain variables.
Step 4 | (Optional) In PulseUno: Create a chain that detects OpenText Functional Testing tests and sends information about them to OpenText Software Delivery Management. See Create a chain to discover tests.
Step 5 | In OpenText Software Delivery Management: Add a PulseUno CI server.
Step 6 | In OpenText Software Delivery Management: Create a pipeline to which PulseUno sends OpenText Functional Testing test results. Set up the pipeline to run on the PulseUno CI server and use the test runner chain.
Step 7 | In OpenText Software Delivery Management: Create a test runner with the following settings: Framework. Select JUnit or any other framework except OpenText Functional Testing. The OpenText Functional Testing framework doesn't support PulseUno CI servers. CI server. Select the PulseUno CI server. Job. Select the OpenText Functional Testing test runner chain you have created in PulseUno.

For details on how to complete the tasks in OpenText Software Delivery Management and trigger automated tests from a test suite, see the OpenText Software Delivery Management help.

Back to top

## Create a chain to discover tests

To detect OpenText Functional Testing tests and inform OpenText Software Delivery Management about them, configure a chain with the plugin Publish UFT One Discovered Tests to Octane.

Note: Administrator, owner, or maintainer permissions required.

To configure a chain that detects OpenText Functional Testing tests:

1. In PulseUno, on the top navigation bar, select the relevant space from the spaces list.

2. On the Products page, open the product or Git repository from which to publish to OpenText Software Delivery Management.

3. On the sidebar, select Chains.

4. Open the chain you want to use for the integration, and click Edit.

   Or create a new chain, as described in Create chains.

5. In the Steps tab, click Add step to chain .

6. From the Add Step list, add the Publish UFT One Discovered Tests to Octane plugin.

7. Click the step and enter the following configuration details:

   Field | Description
   --- | ---
   Title | (Optional) Rename the plugin step.
   Control options | (Optional) Define the control options for the plugin step: Enable step. By default, the step is enabled to run. Clear this option if you need to deactivate the step. Deactivated steps are skipped when the chain runs. Fail the step. Specify the conditions for failing the step, such as unit test failures, findings criteria, and/or console log entries. Mark step as unstable. Specify the conditions for making the step unstable, such as unit test failures, findings criteria, and/or console log entries.
   Output variables | (Optional) Specify the output variables to be passed to other steps down the chain. For details, see Publish output variables.

8. To specify the schedule or the conditions for running the chain, select the Triggers tab and set the Run chain option.

   For example, to discover OpenText Functional Testing tests as soon as they are delivered to your workspace, select to run the chain on every changeset.

   For details, see Schedule chain runs.

9. Click Save & Continue.

Before you can run the chain, finish setting up the integration, as described in Integration steps.

Back to top

See also:

- Use plugins
- View chain runs

https://admhelp.microfocus.com PulseUno 8942
Tips to improve your search results... PulseUno Help Center PulseUno Help 24.2 - 25.2 All View Local Help Center View Online Help Center Version: