FAQ: Squash offers for automated testing
Why the transition from three products (Squash TM, Squash AUTOM, and Squash DEVOPS) to one ?
Henix is changing its offering on January 1st, 2024, by consolidating the Squash range into a single product available in three license levels:
- Community Offer: Tester's operational tool
This offer is free and largely open-source (the web application code is available at https://gitlab.com/henixdevelopment/open-source/squash, and the OpenTestFactory test orchestrator code is available at https://gitlab.com/henixdevelopment/open-source/opentestfactory).
It supports all use cases and aims to be widely used by entities of all sizes, professionalizing testing to state-of-the-art levels. - Premium Offer: Advanced features for increased productivity and/or comfort
- Ultimate Offer: Specific features for intensive use by large accounts and integration with proprietary automation studios
The goal is to align with our vision of Squash: being the testing tool in all its forms.
- Whether for a team working in a V-cycle or agile (XP, Scrum, SAFe, etc.).
- Whether it's testing during the sprint (Q2) or in the acceptance phase (Q3).
(Q2 and Q3 are test quadrants as defined by Brian Marick.) - Whether it's manual testing or automated testing.
- ...
The rationale for this decision and the changes it brings are described in an article on our blog.
What functionalities are added by Premium and Ultimate licenses?
The following table provides an overview of the functionalities by license level:
(To benefit from these or request more information, visit our website or contact us.)
| Squash Community | Squash Premium👑 | Squash Ultimate💎 |
|---|---|---|
| Test automation | ||
| - Support of open-source test frameworks: Cypress, Cucumber JVM, JUnit, Postman, Robot Framework, SKF (Squash Keyword Framework), and SoapUI. | ||
| - Support of proprietary test studios: Agilitest, Katalon, Ranorex, and UFT. | ||
| - Association of automated scripts to Squash TM test cases. | ||
| - Management in Squash TM of the process of test case automation. | ||
| - Management in Jira of the process of test case automation. | ||
| - Generation of Robot Framework or Cucumber scripts from BDD Squash TM test cases. - Transmission of these scripts in a Git repository. |
||
| - Action library for BDD Squash TM test cases. | ||
| Test execution from Squash TM | ||
| - Definition of execution plans in Squash TM. | ||
| - Launch of an execution from Squash TM. - Transmission of environment variables and the test case's custom fields to the automated script. |
||
| - Transmission of custom fields of the iteration, the test suite, and the campaign to the automated script. | ||
| - Set up of an additional configuration of the orchestrator from Squash TM. | ||
| - Publication of test results and reports in Squash TM. | ||
| - Transmission of custom fields of the iteration, the test suite, and the campaign to the automated script. | ||
| Integration with a CI/CD | ||
| - Launch of a Squash TM execution plan from a CI/CD pipeline. - Transmission of the test case custom fields to the script. |
||
| - Filtering of the tests of a Squash TM execution plan depending on custom fields. - Transmission of the custom fields of the iteration, the test suite, and the campaign to the automated script. |
||
| - Publication of test results and reports in Squash TM. | ||
| - Use of a Jenkins plugin for improved user experience. | ||
| - Definition of a quality gate: a list of rules, each defining a scope of the tests to consider and a minimal success rate threshold. - Consideration of the test case's metadata and custom fields by quality gate scopes. |
||
| - Consideration of the custom fields of the iteration, the test suite, and the campaign by quality gate scopes. | ||
| - Publication of quality gate results in GitLab. | ||
| Support | ||
| - No Henix support (a forum is available). | - Henix support. | |