Skip to content

Installation guide


Due to some security issues, it is strongly advised to use Squash TM 1.22.9 (or higher 1.X.Y), 2.2.0 (or higher 2.X.Y), or 3.0.0 (or higher 3.X.Y).

This page describes how to install one by one all the components of Squash DEVOPS.
† indicates a component which is common to Squash AUTOM and Squash DEVOPS. It must be installed only once.


Overview of Squash AUTOM and Squash DEVOPS components

Architecture diagram


Diagram of all interconnections

Squash Orchestrator†

Installation vignette orchestrateur


The installation of the orchestrator consists in deploying an "all-in-one" Docker image. It contains all core services (part of the OpenTestFactory Orchestrator) and some Squash specific services.

To get the latest image of Squash Orchestrator, use the following command:

docker pull squashtest/squash-orchestrator:latest

Preconizations for sizing the Docker container are:

  • 2 CPU
  • RAM: 5 GB (8 GB recommended)
  • disk: provide the capacity for storing the execution reports and their attachments for one hour of usage

Accessibility of the Squash TM instance

Check that the Squash TM instance is accessible from Squash Orchestrator. To do this, go onto the Docker host and run the command (replacing with the URL of your instance):

The answer should be:
Squash is Alive!
If not, resolve the issue with your network administrators.


Configuring the image

The execution of the following command will start the Squash Orchestrator using an existing execution environment, with self-generated trusted keys (which is not recommended in a production setup):

docker run -d \
         --name orchestrator \
         -p 7774:7774 \
         -p 7775:7775 \
         -p 7776:7776 \
         -p 38368:38368 \
         -p 24368:24368 \
         -p 12312:12312 \
         -e SSH_CHANNEL_HOST=the_environment_ip_or_hostname \
         -e SSH_CHANNEL_USER=user \
         -e SSH_CHANNEL_PASSWORD=secret \
         -e SSH_CHANNEL_TAGS=ssh,linux,robotframework \

It exposes the following services on the corresponding ports:

  • receptionist (port 7774)
  • observer (port 7775)
  • killswitch (port 7776)
  • eventbus (port 38368)
  • agent channel (port 24368)
  • quality gate (port 12312)

Additionally, if you want to declare some agents, port 24368 must be exposed. If you want to use the quality gate, port 12312 must be exposed.

For more details about Squash Orchestrator configuration, please check the OpenTestFactory Orchestrator documentation on which Squash Orchestrator is based (the deployment of the two orchestrators is similar). That documentation also details the specific cases of deploying with docker-compose or with Kubernetes.

Run the image in Premium mode

If you have a Premium license for Squash DEVOPS and have deployed the Premium version of the Test Plan Retriever Squash TM plugin, you must run Squash Orchestrator in Premium mode in order to have access to Premium behavior for retrieving the custom fields from Squash TM. In order to do that, you have to add the following parameter in the Squash Orchestrator's run command: -e SQUASH_LICENCE_TYPE=premium.

Orchestrator tools†

Installation vignette of tools


The orchestrator tools aim at simplifying the use of that one. They can be installed on any machine from where we want to administrate the orchestrator.
They require Python 3.8 or later. They are usable on Linux, maxOS, or Windows.

These tools can be installed from PyPI by using the following command:

pip install --upgrade opentf-tools

Overview of the tool capabilities

  • opentf-ready waits until the orchestrator is ready to accept workflows.

  • opentf-done waits until the orchestrator can be safely stopped (i.e. it has no more pending tasks).

  • opentf-ctl can be used to

    • start / track / stop a workflow
    • generate a signed token
    • list the agents
    • generate / modify a configuration file
    • …


A complete description of the tools is available in the OpenTestFactory documentation.

OpenTestFactory Agent†

Installation vignette of agent


The OpenTestFactory agent is a Python application that is installed in the execution environment. It requires Python 3.7 or higher. It works on Linux, macOS, and Windows.

The agent is a simple script. It only has one external dependency, the well known requests Python library (it will be installed if not already present on the execution environment).

To install the agent from PyPI, use the following command:

pip install --upgrade opentf-agent

You can test your installation by running the following command:

opentf-agent --help



$ opentf-agent --help
usage: opentf-agent [-h] --tags TAGS --host HOST [--port PORT] [--path_prefix PATH_PREFIX] [--token TOKEN] [--encoding ENCODING] [--script_path SCRIPT_PATH] [--workspace_dir WORKSPACE_DIR] [--name NAME] [--polling_delay POLLING_DELAY] [--liveness_probe LIVENESS_PROBE] [--retry RETRY] [--debug]

OpenTestFactory Agent

optional arguments:
  -h, --help            show this help message and exit
  --tags TAGS           a comma-separated list of tags (e.g. windows,robotframework)
  --host HOST           target host with protocol (e.g. https://example.local)
  --port PORT           target port (default to 24368)
  --path_prefix PATH_PREFIX
                        target context path (default to no context path)
  --token TOKEN         token
  --encoding ENCODING   encoding on the console side (defaults to utf-8)
  --script_path SCRIPT_PATH
                        where to put temporary files (defaults to current directory)
  --workspace_dir WORKSPACE_DIR
                        where to put workspaces (defaults to current directory)
  --name NAME           agent name (defaults to "test agent")
  --polling_delay POLLING_DELAY
                        polling delay in seconds (default to 5)
  --liveness_probe LIVENESS_PROBE
                        liveness probe in seconds (default to 300 seconds)
  --retry RETRY         how many time to try joining host (default to 5,
                      0 = try forever)
  --debug               whether to log debug informations.


Assuming there is a Squash Orchestrator running on, with a known token stored in the TOKEN environment variable, the following command will register the Windows-based execution environment and will possibly receive commands from Squash Orchestrator targeting windows and/or robotframework tagged environments:

chcp 65001
opentf-agent --tags windows,robotframework --host --token %TOKEN%

The agent will poll the Orchestrator every 5 seconds, and will execute the received commands. The chcp command sets the console to Unicode. It is Windows-specific. It is not mandatory but may be needed depending on the test framework available in the execution environment.


A complete description of the agent is available in the OpenTestFactory documentation.

Test environments†

Installation vignette of test environment

Some test technologies require that some particular components are installed in the test environment, these ones are indicated in the pages describing the specificities of each technology.

Squash TM plugins

Installation vignette of TM Plugins for Squash AUTOM


For details on the installation, please refer to the installation protocol of a Squash TM plugin.

Plugin Squash TM version Compatible plugin version Download latest Community version Download latest Premium version
Result Publisher† 1.22.9, or later 1.X.Y 1.1.X 1.1.0: .tar.gz or .zip 1.1.0: .tar.gz or .zip
2.2.0, or later 2.X.Y 2.2.X 2.2.0: .tar.gz or .zip 2.2.0: .tar.gz or .zip
3.0.0, or later 3.X.Y 3.0.X 3.0.0: .tar.gz or .zip 3.0.0: .tar.gz or .zip
Test Plan Retriever 1.22.9 (or later 1.X.Y) 1.0.X 1.0.0: .tar.gz or .zip 1.0.0: .tar.gz or .zip
2.2.0, or later 2.X.Y 2.0.X 2.0.0: .tar.gz or .zip 2.0.0: .tar.gz or .zip
3.0.0, or later 3.X.Y 3.0.X 3.0.0: .tar.gz or .zip 3.0.0: .tar.gz or .zip

Squash TM configuration

TM configuration vignette


Squash DEVOPS requires that the public URL of Squash TM is defined (see Squash TM documentation).

Plugin for Jenkins

Installation vignette of Plugin Jenkins


The plugin is freely downloadable, as a .hpi file (opentestfactory-orchestrator-1.4.0.hpi).

To install it, you have to submit the plugin in the Upload Plugin area accessible by the Advanced tab of the Plugin Manager in Jenkins configuration:

Upload of Jenkins plugin

Compatibility of the plugin

This plugin is compatible with version 2.164.1 or higher of Jenkins

Back to top