Skip to content

Automation with SKF

Test reference in Squash TM

In order to bind a Squash TM test case to a SKF automated test, the content of the Automated test reference field of the Automation block of a test case must have the following format:

[1] / [2] . [3] # [4]


  • [1]: Path to the root SKF folder (which contains the pom.xml file) on the source repository.

  • [2]: Default test ecosystem of the SKF project (tests).

  • [3]: Child tests ecosystem (it is possible to add several by separating them by .; this parameter is optional).

  • [4]: Name of the test script to run (with its .ta extension; this parameter is mandatory)

Nature of the exploitable Squash TM parameters

The exploitable Squash TM parameters in a SKF script will differ depending on whether you're using the Community or Premium version of Squash DEVOPS.

Here is a table showing the exploitable parameters (these parameters are transmitted as test parameters, see below, Squash TM does not generate global parameters):

Nature Key Community Premium
Name of the dataset DSNAME βœ… βœ…
Dataset parameter DS_[name] βœ… βœ…
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.

Parameters usage

It is possible, when running SKF 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 skf/params action.

Test parameters are available in SKF as script context parameters.
Global parameters are available as global context parameters.

In order to achieve this, it is necessary to (see the SKF documentation):

  • Call the desired parameters inside the files used by the SKF test by using the ${key} syntax.

  • In the SKF test, use the following command to replace, in a file, the parameter references by the values transmitted at execution:
    CONVERT {resourceToConvert<Res:file>} TO file (param) USING context_global_params, context_script_params AS {converted<Res:file>}


Below is an example of a SKF project using a parameter in a XML file and the corresponding Squash TM test case automation:

SKF example

SKF example

SKF example

SKF example

SKF example

SKF example

Supported versions

Squash AUTOM and Squash DEVOPS have been validated with SKF 1.14.0.

Back to top