Configure the Automation of a Project
In Squash TM, an administrator or project leader can configure the automation for each project.
As an administrator or project leader, you can do most of the configuration on the project's configuration page, in the "Automation" block.
Configure the Parameters of BDD Test Cases of the Project
For each project, you can define the technology and language of the scripts that were exported or transmitted from the BDD test cases written within the project.
To learn more about these two parameters, please visit this page Implementation Technology and Script Languages.
Associate a Test Automation Server with a Project
The configuration of the test automation server slightly differs depending on the tool used to execute automated tests (Squash orchestrator or Jenkins).
If the tool used is the Squash Orchestrator (Squash AUTOM), just associate the server you created with the project. It is then possible, but not mandatory, to define a token at the project level and/or default environment tags and default environment variables.
If the tool used is Jenkins, link the server you created with the project; and also the jobs containing the scripts to execute from Squash TM.
To learn more about how to configure a test automation server for a project, please visit this page: Associate a test automation server.
Activate the Automation Workflow
To track the automation of Squash TM test cases, the tool offers three automation workflows. An advanced Squash workflow driven by the automation workspace, a simple Squash workflow managed on the test case page and a distant workflow managed in Jira that enables you to set up a custom workflow and track its progress thanks to Jira issues.
You can activate the automation workflow from a project's configuration page, in the Automation block.
To learn more about these automation workflows, please visit these pages:
Associate a Source Code Management Server with a Repository
Squash TM enables you to transmit scripted test cases (BDD and Gherkin) written in Squash TM to a GitHub, GitLab or Bitbucket source code management server.
For this, you must associate a source code management server and repository with your Squash TM project.
To configure a source code management server in a project, please visit this page: Associate a source code management server.
For a project configured with a Jenkins server, if the source code management server configured in the project is the same as the one configured in the job associated with the project Squash TM, and if the "Can execute BDD" option is checked, the automated scripts are automatically associated with the scripted test cases (Gherkin or BDD).
Warning: In that case, we recommend that you have only one job that can execute BDD scripts in the Job table.
For a project configured with a Squash AUTOM server, if a repository for the source code management server is configured in the project, the Squash AUTOM fields "Automated test technology", "Source code repository URL", "Automated test reference" are automatically completed during the transmission of the test cases.
Activate the Result Publisher Plugin (Squash AUTOM)
The Result publisher plugin enables you to retrieve the results and details of the executions, and the execution reports of the automated tests executed using the Squash orchestrator.
To configure this plugin, activate it in the project from the plugins tab. When the Premium version of the plugin is installed, you can retrieve more information about the execution. For this, you must activate full data reporting.
To configure the Result publisher plugin in a project, please visit the page Configure the Result publisher plugin.