FAQ: The transition from Squash TF to Squash AUTOM and Squash DEVOPS
Will new features for Squash TF be developed in the future?
No, there will be no new features developed for Squash TF.
We encourage you to make the transition from Squash TF to Squash AUTOM for the execution of your automated test assets in order to take advantage of all the new features offered by Squash.
Nevertheless, the elements of Squash TF will remain available for download. Likewise, the open source repositories will remain accessible.
Does support for Squash TF end with the release of Squash AUTOM and Squash DEVOPS?
We will continue to provide support on Squash TF via the Squashtest forum and, for customers of the Squash AUTOM commercial offer, via our support service.
Does my legacy of automated tests, previously run with Squash TF, need to be modified to be used with Squash AUTOM?
The scripts/automated tests that you run via Squash TF can be used by Squash AUTOM without any modification.
Can I run SKF tests with Squash AUTOM and Squash DEVOPS?
SKF tests are supported since version 2021-07.
What do I need to do in Squash TM to run my automated execution plans with Squash AUTOM instead of Squash TF?
It is necessary to create a link between a Squash TM test case and your automated test according to the Squash AUTOM documentation.
This action is almost instantaneous and can be done, at the same time, for several Squash TM Gherkin or BDD test cases using the Git plugin.
For the other test cases, an action on each test case will be necessary according to the Squash AUTOM documentation.
The link action between a Squash TM test case and an automated test for an execution with Squash AUTOM is different from the one for an execution with Squash TF.
Can I mix in the same execution plan automated test cases executed by Squash TF and test cases executed by Squash AUTOM?
In order to ease the transition, it is perfectly possible to have test cases from a project running Squash TF and test cases from a project running Squash AUTOM within the same Squash TM execution plan.