The version 4.0 of Squash TM is available for download.
This version includes the following evolutions:
Integration with GitLab in agile context
Selection of the execution environment when launching automated tests with Squash AUTOM
Advanced declaration of issues in Mantis
Redesign of editable requirement and test case reports
Import / Export and high level requirements in dashboards
Optimization of the display and export of known issues
Xsquash4Jira synchronization with the user's credentials
Filtering of BDD action suggestions on projects
Smaller changes and bug fixes
Discover the main new features of Squash TM 4.0 below.
For the complete list of evolutions and fixes, you can consult the release note of the version.
Please note that with Squash TM 4.0, the version of Java and the drivers for connecting to PostgreSQL and MariaDB databases have been updated. As a result, MySQL and some versions of MariaDB, PostgreSQL and Java (including Java 8) are not compatible with Squash TM 4.0. Find more information in our dedicated article.
Integration with GitLab in agile context
Squash TM 4.0 reinforces the integration with GitLab to allow to manage the tests in relation with the GitLab issues and to ensure a follow-up of the testing activity in GitLab.
This integration allows each team member to work more efficiently using the tool best suited to their needs:
From Squash, testers access GitLab issues content to design, plan and execute tests
From GitLab, other team members can follow the progress of tests
This integration is done via an Xsquash4GitLab plugin (which is compatible with GitLab.com and GitLab EE Self-Managed but not with GitLab CE Self-Managed) and offers the following features:
Synchronization of GitLab issues as Squash requirements and association with test assets
The issues to be synchronized can be contained in a GitLab project or group and it is possible to apply filters on the fields or to indicate the GitLab board in which they are located to refine the selection. In Squash, the synchronized issues can be organized by iteration, milestone or project in order to have a view by sprint, by version or a hierarchical view.
As with Squash's native requirements, they are then linked to test cases to ensure coverage.
Tracking coverage and success rate of issues in GitLab
In GitLab, there are metrics to track the coverage, redaction and execution progress of the tests for each issue. These indicators are displayed as a comment.
Selection of the execution environment when launching automated tests with Squash AUTOM
With Squash AUTOM, automated tests can now be run on a user-selected environment.
Execution environments are represented by tags whose values are returned by Squash Orchestrator.
In Squash TM, default environment tag values can be set at the test automation server and project level.
These values are proposed by default to the user when launching automated tests. Nevertheless, he can select others in order to target another environment on which to run the tests.
For Squash AUTOM/DEVOPS users, we recommend that you upgrade to the latest 2022-07 release to take advantage of the full functionality. For more information, consult the release note.
Advanced issue reporting in Mantis
A new Mantis Bugtracker plugin is available. It uses Mantis REST API and replaces the previous connector, based on Mantis SOAP API.
With this plugin, the issue reporting in Mantis now takes into account all fields (including the addition of attachments) as well as the settings made in Mantis (custom fields, default values).
Switching from the old to the new plugin does not result in any loss of data, anomalies attached to executions will still be visible in Squash TM. Only the authentication protocol changes, it is now done by token. Users have to authenticate again to Mantis from Squash TM by entering their token generated in Mantis.
Redesign of the editable requirements and test case reports
The editable requirements and test case reports have been redesigned. In particular, they offer a more readable and condensed display of data.
Here are other evolutions that this redesign brings:
Contents and numbering follow the tree structure defined in Squash TM
High level requirements are taken into account
New printing options are available (folder information, association with test cases and requirements for the requirement report)
Import / Export and high level requirements taken into account in dashboards
It is now possible to import and export high-level requirements as well as their links with standard requirements.
High-level requirements are also taken into account in the dashboards. Test cases indirectly linked to high-level requirements are included in the requirement coverage charts. As in the search, an option allows you to extend the scope of high-level requirements so that the dashboards take into account the attached standard requirements, even if they are not in the initial selection.
High-level requirements management is a feature available with the Squash TM Premium license.
Optimization of the display and export of known issues
When the same issue is attached to several executions, it is now displayed only once in the "Known issues" tables of Squash TM.
These same tables can be exported to .csv format.
Xsquash4Jira synchronization with a user's credentials
Xsquash4Jira synchronizations can be done with a user's credentials instead of the synchronization server's credentials. This feature allows to have more control the synchronization perimeters and to avoid the multiplication of the synchronization servers.
Filtering of BDD action suggestions on projects
When writing BDD test cases, it is now possible to filter the action suggestions by project. This makes it easier to search the action library and makes the suggestions more relevant as they are limited to one or more projects selected by the user.
This feature is available with the "Action words Library" plugin (Squash AUTOM Premium license).