Piloting automated test executions from Squash TM
Squash TM test case automation
Info
This page describes the operations common to all supported test frameworks. You can access the automation specificities for each technology directly with the following links:
One technology per Git repository
Squash Orchestrator currently supports only one test technology per Git repository.
Specifically, it is not possible to launch a test iteration/suite containing tests from the same Git repository but using different technologies.
Without using the Squash automation workflow
To execute a test case using the Squash Orchestrator, its Automation block 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. -
Source code repository URL: The address of the source code repository where the project is located, as referenced in the Source code management servers area of the Administration. -
Automated test reference: This is the location of the automated test within the project. This reference must follow the specific format of the used test technology.
Using the Squash automation workflow
Regular test case
To execute a test case using the Squash Orchestrator, it must be automated in the Automation Workspace by filling three columns:
-
TECHNO.: A dropdown list allowing you to choose the technology used for the execution of a test case. -
SCM URL: The address of the source code repository where the project is located. -
REF. OF THE AUTO TEST: This is the location of the automated test within the project. This reference must follow the specific format of the used test technology.
BDD or Gherkin test case
The information of the Automation block is automatically filled during the transmission of a BDD or Gherkin script to a remote source code repository hosting service. It can also be modified by the user at any moment.
Squash TM parameters exploitation
When a Squash TM execution plan is launched (from Squash TM or a CI/CD pipeline), Squash TM will transmit various information on execution plan item that can be exploited by a test case. Details of this functionality can be found on the corresponding used technology section.
Info
The following frameworks can exploit Squash TM parameters during test execution:
- Agilitest‡
- Cucumber JVM
- Cypress
- JUnit
- Katalon‡
- Postman
- Ranorex‡
- Robot Framework
- SKF
- UFT‡
Automated suite execution
The steps to run an automated test plan in Squash TM are the usual ones:
-
Get to the execution plan of the selected Iteration or Test Suite.
-
Run the test using one of the buttons on the screen below:
- An Overview of automated test executions popup shows up.
Info
The execution overview popup contains a new section displaying the ongoing executions performed by the Squash Orchestrator. However, the state of the executions are not updated once launched in the current version.
Execution order of tests
The only order assured by Squash AUTOM (resp. Squash DEVOPS) is that, for a given Git repository in a given iteration/test suite, the tests will be executed in the order defined in Squash TM.
If a test iteration/suite contains automated tests belonging to multiple Git repositories, the order of execution of tests from one repository relative to the execution of tests from another repository is undefined.
If several test iterations/suites are launched from Squash TM (resp. the CI/CD pipeline), the order of execution of the tests of one iteration/suite relative to the execution of the tests of another iteration/suite is undefined. (Except in the trivial case where a suitable execution environment is available and the first suite/iteration was able to start before the Squash TM user – resp. the CI/CD pipeline – launches another one.)
Published results after a Squash TM test plan execution
Independently from the means used to trigger a test plan execution (from Squash TM or a CI/CD pipeline), the kind of results published in Squash TM at the end of the execution of a test plan will differ depending on your using 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 information is updated:
-
ITPIs (Iteration Test Plan Item, see the Squash TM glossary) status update.
-
Automated suite status update.
-
The Allure report (file
allure-report.tar) and the Squash Orchestrator logs (fileexecutionlog.txt) corresponding to all the executed tests. -
The various ITPIs execution reports are accessible from the Automated Suites tab of the iteration or test suite:
Info
All the results from the automated suite are compiled in an Allure type report, available in the allure-report.tar archive.
For more information on how to exploit the Allure report, please refer to the Allure documentation.
Squash AUTOM Premium
If you are using the Squash AUTOM Premium components, you have access to two types of results publication:
- Light (default value);
- Full.
The choice of publication type is operated on a project basis by accessing the configuration of the Squash TM Result Publisher plugin from the Plugins tab of your project page, inside the Administration Tab:
Light results publication
By choosing the "Light" results publication, the same information is available as for Squash AUTOM Community.
Full results publication
By choosing the "Full" results publication, the same information is available as for Squash AUTOM Community but with the addition of:
-
A new execution is created for each executed ITPI.
-
The execution reports of the various executions can also be accessed from the execution page (the reports are present in the attached files):
Legend
†indicates a component which is common to Squash AUTOM and Squash DEVOPS.
️‡ indicates a Premium component. An overview of the Premium features is available here. To benefit from these or to ask for more information, check our website or contact us.