Piloting automated tests executions from Squash TM¶
Squash TM test case automation¶
Without using the Squash automation workflow¶
For a test case to be usable by the Squash Orchestrator, its Automation panel in the Information tab of the test case page must be correctly filled :
Automated test technology
: A dropdown list allowing you to choose the technology used for the execution of a test case. In this version, only Robot Framework and Junit are functioning.Source code repository URL
: The address of the source code repository where the project is located.Automated test reference
: This is the location of the automated test within the project. This reference must follow the format specific to the test technology used (see here).
Using the Squash automation workflow¶
Regular test case¶
For a test case to be usable by the Squash Orchestrator, it must be automated in the Automation Workspace by filling three columns :
Auto. test tech.
: A dropdown list allowing you to choose the technology used for the execution of a test case. In this version, only Robot Framework and Junit are functioning.Scm URL
: The address of the source code repository where the project is located.Auto. test ref.
: This is the location of the automated test within the project. This reference must follow the format specific to the test technology used (see here).
Warning
A known issue of this version is the lack of repository name at the begining of the reference when automatically filled by Squash TM. It is therefore necessary to add it manually. This name is the last part of the source code repository URL.
BDD or Gherkin test case¶
The informations of the Automation panel are automatically filled during the transmission of a BDD or Gherkin script to a remote source code repository host service. They can also be modified by the user at any moment.
Automation frameworks specifics¶
Automation with Robot Framework¶
In order to bind a Squash TM test case with a Robot Framework automated test, the content of the Automated test reference field of the Automation panel of a test case must have the following format :
[1] / [2] # [3]
With :
[1]
: Name of the project on the source code repository.[2]
: Path and name of the Robot Framework test, from the root of the project (with the.robot
extension).[3]
: Name of the test case to execute in the.robot
file.
Below is an exemple of a .robot
file and the corresponding Squash TM test case automation :
Automation with JUnit¶
In order to bind a Squash TM test case with a JUnit automated test, the content of the Automated test reference field of the Automation panel of a test case must have the following format :
[1] / [2] # [3]
With :
[1]
: Name of the project on the source code repository.[2]
: Qualified name of the test class.[3]
: Name of the method to test in the test class.
Below is an exemple of a test class and the corresponding Squash TM test case automation :
Test plan execution from Squah TM¶
This functionnality is not available in the 1.0.0.alpha1 version.
It is however possible to trigger the execution of a Squash TM test plan from a Jenkins pipeline. Please refer to the Squash DEVOPS user guide.
Results publication after a Squash TM test plan execution¶
Independently from the means used to trigger a test plan execution (from Squash TM or a Jenkins pipeline), the kind of results published in Squash TM at the end of the execution of a test plan will differ depending on the usage of a Squash AUTOM Community or Squash AUTOM Premium licence.
Squash AUTOM Community¶
After the execution of a Squash TM test plan (iteration or test suite), the following informations are updated :
ITPIs status update.
Automated suite status update.
The various ITPIs execution reports are accessible from the Automated Suites tab of the iteration or test suite :
This, however, doesn’t happen :
Creation of a new execution for each executed ITPI.