UFT Integration V1

This feature is available in qTest Elite and Enterprise packages. We provide a command line tool which is capable of kicking off UFT scripts which reside on your local machine and reporting back to qTest. Automation Test Cases and Test Runs are automatically created in qTest so you will not need to manually create them.

In order to setup the integration, please follow the steps below:

  1. Enable Automation Integration settings for your qTest project
  2. Download our UFT Integration command line tool and set it up on the same machine where your UFT tests are executed

  IMPORTANT:

  • UFT and the UFT Integration tool need to be installed on the same machine, in order for the UFT Integration tool to kick off UFT scripts
  • The integration tool works with UFT v12.52

See our instructions below:

»Enabling Automation Integration feature in qTest

»Executing UFT Integration tool

Enabling Automation Integration feature in qTest

In order to receive test results submitted by the UFT Integration tool, you will need to activate the Automation Integration feature in your qTest project.

  1. Access your qTest project, click on the Gear icon and select Automation Settings
  2. Switch on the Activation Status
  3. Map automation execution results with corresponding qTest values. Map UFT test results with corresponding execution status in qTest. The default UFT results include:
    • PASSED
    • FAILED
    • WARNING
    • DONE
  4. Click on the Save button

qTest - Automation Settings - UFT

Executing UFT Integration tool

A. Download UFT Integration tool

  1. Access the qTest Resources page
  2. Download the qtestuft.exe file

qTest - Resources - Download UFT

B. Available Arguments

After you have downloaded the exe file, open the Console and execute this command to see all available arguments.

qtestuft.exe -h

qtestuft - help

Argument Required Value/Description

-u

--qtest-url

Yes The URL to access to your qTest instance

-t

--token

Yes

The token to login to your qTest instance. You can get the token from the qTest Resources page

qTest - Resources - UFT Token

-p

--project-id

Yes ID of the qTest project to which you want to report test execution results to. You can get the project ID from its URL or from the Site Administration Projects page: 
qTest - Project ID

-s

--test-suite-id

No

When test results are submitted to qTest, Test Runs are automatically created in qTest if they do not already exist.

You can specify a qTest Test Suite where the submitted Test Runs will be located using its ID or PID.

If it is omitted, one Test Suite is created per execution date to contain the Test Runs. If UFT tests are executed multiple times in one day, all Test Runs are located in the same Test Suite of that day. The Test Suite is named as UFT yyyy-mm-dd, in which yyyy-mm-dd is the execution date, and it is located under the Test Execution tree's root.

-d

--execution-date

No

Specify an execution date in yyyy-mm-dd which will be used in the default Test Suite name.

If it is omitted, qTest will used the test log submitted date to create the Test Suite.

-m

--module-id

No

When test results are submitted to qTest, Test Cases are automatically created in qTest if they do not already exist.

All eggPlant Test Cases are located under the UFT Automation module located under the Test Design tree's root.

If you specify a parent module using its PID or ID, the UFT Automation module will be created under the parent module.

<folder ...> Yes Directories in which UFT tests are located. You can specify multiple directories, separated by a blank space. You can use a wildcard to specify multiple directories
  • ? matches one character
  • * (asterisk) matches zero or more characters

-S

--save-config

No Save the configuration specified in the above arguments in the config.ini file which is located under the same directory as qtestuft.exe. You can re-use the configurations in the next execution without specifying them via arguments.

C. Execute UFT Integration tool

  1. From the Console, execute qtestuft.exe and pass in configurations for required arguments
  2. Submission progress is logged in the console, so you can monitor it
    Snap 2016-07-14 at 01.56.06
  3. After the submission is completed, you can access your qTest project to verify if Test Cases and Test Runs have been created

  NOTE:

  • Configurations can be defined in either the configuration file or via command line arguments. If the same configuration is defined in both places, the UFT Integration tool will use the configurations in the command line arguments
  • One UFT test is created as one Test Case in qTest and its actions are created as Test Steps