Automation with Agilitest
This feature is available only in the Premium version of Squash AUTOM.
Test reference in Squash TM
In order to bind a Squash TM test case to an Agilitest automated test, the content of the Automated test reference field of the Automation block of a test case must have the following format:
 / 
: Name of the project on the source code repository.
: Path and name of the ActionTestScript file, from the root of the project (with the
The ATS script must be located in
src/main/ats/* , as in any regular ATS project architecture.
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 Agilitest 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
The parameters are available in Agilitest as environment variables and can be retrieved using the
$env(parameter_name) function (see the Agilitest documentation). If the same name is used both for a global parameter and a test parameter, the last one is used.
Below is an example of an Agilitest test file and the corresponding Squash TM test case automation:
Squash AUTOM and Squash DEVOPS have been validated with ATS 2.3.0. Any recent version should work properly.