Automation with UFT
This feature is available only in the Premium version of Squash AUTOM.
Squash AUTOM/Squash DEVOPS current version only supports "GUI Testing". "API Testing" and "BPT Testing" are not available yet.
The result publication in Squash TM requires UFT be configured to generate a "Run Result Viewer Report":
(This configuration is tied to the test, so it has to be committed in the Git repository.)
Test reference in Squash TM
In order to bind a Squash TM test case to a UFT automated test, the content of the Automated test reference field of the Automation block of a test case must have the following format:
: The path to the test folder to execute.
Nature of the exploitable Squash TM parameters
Here is a table showing the exploitable parameters (these parameters are transmitted as test parameters, see below, Squash TM does not generate global parameters):
|Name of the dataset||DSNAME|
|Test case reference||TC_REFERENCE|
|Test case custom field||TC_CUF_[code]|
|Iteration custom field||IT_CUF_[code]|
|Campaign custom field||CPG_CUF_[code]|
|Test suite custom field||TS_CUF_[code]|
[code]: Value of the "Code" of a custom field
[name]: Parameter name as filled in Squash TM
As indicated, Squash TM adds a prefix to the code of the transmitted custom field. Make sure to take it into account.
Refer to the Squash TM documentation for more information about custom fields.
It is possible, when running UFT tests, to exploit parameters within it. A parameter can be a test parameter or a global parameter. Squash TM transmits only test parameters. Test parameters and global parameters can be used in Squash DevOps with the
Each parameter is available in UFT as a test parameter (see the UFT documentation).
If the same name is used for a global parameter and a test parameter, the latter is taken into account in UFT.
Below is an example of a UFT solution and the corresponding Squash TM test case automation:
Squash AUTOM and Squash DEVOPS have been validated with UFT 15.0.2. Any recent version should work properly.