FAQ: SquashTM offers for automated testing
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.)
| Feature | SquashTM Community | SquashTM Premium👑 | SquashTM Ultimate💎 |
|---|---|---|---|
| Test automation | |||
| - Support of open-source test frameworks: Cypress, Cucumber JVM, JUnit, Playwright, Postman, Robot Framework, SKF (Squash Keyword Framework), and SoapUI. | ☑ | ☑ | ☑ |
| - Support of proprietary test studios: Agilitest, Katalon, Ranorex, and UFT. | ☑ | ||
| - Association of automated scripts to SquashTM test cases. | ☑ | ☑ | ☑ |
| - Management in SquashTM 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 SquashTM test cases. - Transmission of these scripts in a Git repository. | ☑ | ☑ | ☑ |
| - Action library for BDD SquashTM test cases. | ☑ | ||
| Test execution from SquashTM | |||
| - Definition of execution plans in SquashTM. | ☑ | ☑ | ☑ |
| - Launch of an execution from SquashTM. - Transmission of environment variables and the test case's custom fields to the automated script. | ☑ | ☑ | ☑ |
| - Transmission to the automated script of - the custom fields of the iteration, the test suite, and the campaign; - the execution ID (with Squash TM 8.0 or later). | ☑ | ||
| - Set up of an additional configuration of the orchestrator from SquashTM. | ☑ | ||
| - Publication of test results and reports in SquashTM. | ☑ | ☑ | ☑ |
| - Comparison of the results of several executions. | ☑ | ☑ | |
| - Real-time execution log visualization. | ☑ | ☑ | |
| Integration with a CI/CD | |||
| - Launch of a SquashTM execution plan from a CI/CD pipeline. - Transmission of the test case custom fields to the automated script. | ☑ | ☑ | ☑ |
| - Filtering of the tests of a SquashTM execution plan depending on custom fields. - Transmission to the automated script of - the custom fields of the iteration, the test suite, and the campaign; - the execution ID (with Squash TM 8.0 or later). | ☑ | ||
| - Publication of test results and reports in SquashTM. | ☑ | ☑ | ☑ |
| - Comparison of the results of several executions. | ☑ | ☑ | |
| - 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. | ☑ | ☑ | ☑ |
| Import of automated test execution results into Squash TM | |||
| Import of automated test suites and executions via the API. | ☑ | ☑ | ☑ |
| - Import of assertion failures for automated test executions via the API. | ☑ | ☑ | |
| Support | |||
| - Henix support. | No support (a forum is available). | ☑ | ☑ |