Use Azure DevOps Server or Services to run tests from ALM Lab Management

This topic describes how to add Azure DevOps Server build steps to first prepare the ALM Lab environment, and then run OpenText Functional Testing functional tests from the ALM Lab Management module.

In this topic:

Prerequisite

Before you can run OpenText Functional Testing tests from ALM, you must first set up the integration with ALM. This is a one-time setup, which you need to repeat only if you change to another ALM version.

Register the ALM client in Common mode on the machine that the Azure DevOps Server will use to run the OpenText Functional Testing tests. For details on registration, see the ALM Client Launcher section in the ALM Help Center.

Back to top

Prepare the ALM Lab environment

Prepare the ALM Lab environment before running OpenText Functional Testing tests saved in ALM, as part of a test set or build verification suite from the Test Lab Module in ALM.

In Azure DevOps Server:

1. Create a pipeline. (Note: If you are using TFS, skip this step)

   1. Create a build pipeline or a release pipeline, with the Empty job template.

      Note: A build pipeline is the pipeline type created when you do not explicitly create a release pipeline.

   2. Select the agent pool that includes the agent on which you want to run your tests.

   3. In the pipeline variables, add a UFT_LAUNCHER variable. The variable's value should be the full path to the UFTWorking folder.

   For more details, see the Microsoft Azure documentation.

2. Add a UFT One task or build step, in the correct place in the build order:

   1. In the Task catalog, select the Test tab. A list of all available test tasks is displayed.

   2. From the Test tab, select the UFT One ALM Lab Environment Preparation task and click Add. A new, empty task is added as part of your build plan.

3. Provide the following information for your task:

   Display name (optional)	By default, the Azure DevOps Server CI system uses a preset descriptor for the task. Provide a more meaningful name for your step.
   ALM server	The ALM server from which to run the test. The ALM server address must be in one of the following formats: http://<ALM server name> IP:port/qcbin You may also need to connect to ALM using common registration mode. If this is the case, enter the URL using one of the following formats: http://<ALM server name> IP:port/qcbin/start_a.jsp?common=true
   ALM Credentials	Enter the username and password to use to access the ALM server. (SSO authentication is not supported) Ensure that the ALM user you specify has the correct permissions to open and run the OpenText Functional Testing tests. For details on permissions, see the ALM Help Center.
   Domain	The domain in the ALM server where the project containing the tests is stored.
   Project	The project containing the tests.

   To hide sensitive information in Azure

   To hide information such as the ALM password or the SSO credentials, define Azure task variables for this information and lock them:

   1. Create the variable: 

      In the task's Variables tab add a variable for each field whose value you want to hide.

      Enter the value for the variable, select the lock option.

      Tip: Optionally, select Settable at queue time too, to enable editing this value when queueing the build.

      For example, create a MyPassword variable and enter your ALM password as its value.

   2. Link your variable to the relevant field in the task:

      In the Tasks tab, click Link settings.

      In Setting to link, select the field to link to the variable, and in Value, enter $(<variable name>). Click Link to complete the process.

      For example, select the Password field and enter $(MyPassword).

4. Expand the Advanced settings and specify one of the following:

   Create a new configuration named	Enter a name for the configuration. If you select this option, enter the values in the specified fields.
   Use an existing configuration ID	Enter the ID of your AUT Environment configuration in ALM.

   For details on the available options, click the question icon to the next of the option.

5. Expand the Parameters section and enter the AUT Environment parameters you want to update for the configuration.

   You are limited to 10 parameters for this task. If the tests you want to run include more than 10 parameters, add another step.

   Note: You must select each parameter individually (one-by-one), and specify the parameter details.

   Not selecting or providing a parameter value for any parameter will cause the specified parameters to not be used.

6. Configure the CI system control options for the step, including:

   Enabled	Specify whether the step should be run as part of this build
   Continue on error	Instructs the CI system to stop or continue the build if there is an error on this step.

This configuration will be used as a build step in the appropriate place.

Continue with Run OpenText Functional Testing tests from ALM Lab Management.

Back to top

Run OpenText Functional Testing tests from ALM Lab Management

After preparing the ALM Lab environment, add another Azure DevOps Server build step to trigger your OpenText Functional Testing test run.

To trigger a test run from ALM Lab Management:

1. In Azure DevOps Server, do one of the following:

   • Open the pipeline you created earlier, which contains the step for UFT One ALM Lab Environment Preparation task.

   • If your lab environment is already set up and you don't need a preparation task:

     Create a pipeline. (Note: If you are using TFS, skip this step)

     1. Create a build pipeline or a release pipeline, with the Empty job template.

        Note: A build pipeline is the pipeline type created when you do not explicitly create a release pipeline.

     2. Select the agent pool that includes the agent on which you want to run your tests.

     3. In the pipeline variables, add a UFT_LAUNCHER variable. The variable's value should be the full path to the UFTWorking folder.

     For more details, see the Microsoft Azure documentation.

2. Add a UFT One task or build step, in the correct place in the build order:

   1. In the Task catalog, select the Test tab. A list of all available test tasks is displayed.

   2. From the Test tab, select the UFT One ALM Lab Management Run task and click Add.

      A new, empty task is added as part of your build plan.

3. Provide the following information for your task:

   ALM Server	The general information for the tests, including the ALM server information, and the Test Lab identification information. You may also need to connect to ALM using common registration mode. If this is the case, enter the URL format as one of the following: http://<ALM server name> IP:port/qcbin/start_a.jsp?common=true
   ALM credentials	Depending on the authentication type required by your ALM server, credentials can be a username and password or an API key for SSO authentication. Username and password: User name: The ALM user name to use to access the server. Password: The password for the ALM user specified above. SSO authentication: Select SSO enabled. Enter the Client ID and API key secret obtained from your ALM site administrator. Ensure that the ALM user or client specified in this task has the correct permissions to open and run the OpenText Functional Testing tests. For details on permissions, see the ALM Help Center.
   Domain	The domain in the ALM server where the project containing the tests is stored.
   Project	The project containing the tests.
   Run Type	The run mode to use when running the tests: Test set or Build verification suite
   Test Set ID / Build Verification Suite ID	The ID (from ALM) of the test set or build verification suite you want to run. The test set must be of type Functional.
   Timeslot Duration (in minutes, minimum=30)	The amount of time needed on the host to run the test set or build verification suite.
   CDA provisioning information	The details for CDA provisioning on the ALM server. For details on an individual option, click the Information bubble next to the option. For more details, see the ALM Help Center.
   Timestamp pattern	Define the value format of the timestamp field used for reporting in the Extensions tab. The default value is yyyy-MM-dd HH:mm:ss.

4. (Optional) From the Test tab, add a Publish Test Results task or build step to publish test results to Azure Pipelines.

   Note: This option is supported when working with the UFT One Azure DevOps extension version 2.0.3 or later.

   Provide the following information for the step, to create a JUnit report based on OpenText Functional Testing's XML run result report:

   Display name	Specify a name for the step.
   Test result format	JUnit
   Test results files	**/*.xml
   Search folder	Provide the path to the folder that contains the test result XML files. Use the following format:  In a build pipeline: <Path to UFTWorking\res folder>\Report_$(Build.BuildNumber) In a release pipeline: <Path to UFTWorking\res folder>\Report_$(Release.ReleaseID)
   Test run title	Specify a title for the report. Use environment variables in the title as follows, to base the report name on the pipeline name and the build number: In a build pipeline: $(System.DefinitionName)_$(Build.BuildNumber) In a release pipeline: $(System.DefinitionName)_$(Release.ReleaseID) This helps retrieve the report on Azure DevOps.

5. Configure the CI system control options for the step, including:

   Enabled	Specify whether the step should be run as part of this build
   Continue on error	Instructs the CI system to stop or continue the build if there is an error on this step.
   Run this task	Indicates to the CI system when to run this step. To publish the results after running the tests failed, select Even if a previous task has failed, unless the build was canceled.

6. Set your pipeline to run: 

   Build pipeline: Save and queue the pipeline.

   Release pipeline: Create a release and deploy the pipeline.

   When the pipeline runs, the OpenText Functional Testing tests run as part of the task you added.

   The tests run on the hosts configured in the ALM Lab Management setup. Both specific host allocations and Automatch configuration are supported.

Back to top

View the test results

After the test run, you can view the run results in the following ways: 

A visual report

In the Extensions tab of the run results, you can see a report including the following parts: 

• The UFT Report section shows the test run status.

• The Run Summary shows the number of tests that ran and the percentage of each status.

A JUnit test result report

If you added a Publish Test Results step, you can view the JUnit results on the Tests tab of the run results.

A link to the run results that are saved on ALM (if you run the tests from TFS)

OpenText Functional Testing automatically saves a link to the run results on ALM as an artifact with the build.

View this link on the Summary tab of the run results.

For example:

Back to top

See also:

• Test from Azure DevOps Server or Services
• Use Azure DevOps Server or Services to run a test saved in ALM
• Known issues - Running tests from Azure DevOps