Use Azure DevOps Server or Services to trigger a local test

This topic describes how to trigger a UFT One test stored on your local machine from Azure DevOps Server (formerly known as TFS).

Note: This topic describes working with UFT Azure DevOps extension version 2.0.3. To benefit from the latest functionality, we recommend updating existing tasks' versions to 2.*. When using this extension version, make sure that you installed the corresponding UFT.zip file from the ADM-TFS-Extension GitHub repository.

Run a test saved on your local machine

In Azure DevOps Server, do the following:

  1. Create a new empty pipeline using the classic editor (Note: If you are using TFS, skip this step).

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

    For more details, see the Microsoft Azure documentation.

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

    1. From 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 File System Run task and click Add. A new, empty task is added as part of your build plan.

  3. Provide the following information for your build step.

    Description

    By default, the Azure DevOps Server CI system uses a preset descriptor for the task. Click the Rename button and provide a more meaningful name for your step.
    Tests The test, test batch file, or folder containing the tests to run. For multiple tests, the test path, name, or test result path should be separated by a comma.
    Timeout

    The amount of time (in seconds) to wait if there is a problem opening or running a test. If the field is left blank, there is no timeout.
    Generate 'Failed Tests' report

    Select whether to generate a report which provides information on your tests' failed steps. After the run, the report is available in the Extensions tab.

    Alternatively, indicate a batch file that contains a list of tests and their parameters.

    • Specify multiple tests, or the same test several times with different parameters each time.
    • Use the reportPath parameter to define a specific path for your test result.

    The batch file should have an .mtbx extension and use the following syntax:

    <Mtbx>
     <Test name="test1" path="c:\tests\APITest1">
     <Parameter name="A" value="abc" type="string"/>
     ....
     </Test>
     <Test name="test2" path="c:\tests\test2">
      <Parameter name="p1" value="123" type="int"/>
      <Parameter name="p4" value="123" type="float"/>
       ....
     </Test>
     <Test name="test3" path="c:\tests\APITest3" reportPath="c:\reports\APITest3">
    </Mtbx>

  4. (Optional) Configure the run step to upload UFT One's test result information to an Azure Storage location

    Uploading the UFT One results to Azure Storage lets you to access the results from the Azure DevOps portal after the test run.

    Make sure you performed the steps described in Set up Azure Storage for your UFT One test results.

    Then enter the following options in your Run From File System build step:

    Do you want to upload the UFT report to the storage account?

    Select Yes.
    Artifacts to upload

    Select whether to upload only the html run results report, an archive of all the UFT One result files, or both.

    Note: When running an API test we recommend uploading the archive, as the standalone html run results report does not contain any information on the captured data. The content for RequestBody and HttpRawRequest steps is available in the html file contained in the archive.
    Report file name

    Accept the default file name, which is based on the pipeline name and build number, or enter a name of your choice.

  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.
    Always run Instructs the CI system to always run this step.

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, as well as links to the UFT One report and archive, if they were uploaded to Azure Storage.

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

  • If you selected the Generate ‘Failed Tests’ report option, the Failed Tests section shows a detailed breakdown of any failed steps.

Retrieve run result files

  • The detailed failure results are stored in JUnit format in the junitreport.xml file located in the UFTWorking/res/Report_<build run number> folder.

  • If the UFT One html report and the archive file were uploaded to Azure Storage, you can access these in the storage container.

If you run your UFT One tests on Team Foundation Server (TFS)

You can also view UFT One run results in the Summary tab of the TFS build run results.

For example:

Back to top

See also: