Squash TM 2.1 is now available for download.
This new version now supports token authentication to Github. Its new features aim to improve Xsquash4Jira's configuration and synchronizations.
Discover Squash TM 2.1's main new features down below.
For a complete list of evolutions and corrections, please read this version's release note.
Token authentication to Github is now supported
Following Github's new token authentication policy, a new authentication protocol is available on the configuration pages of all source code management servers. This protocol allows you to enter a token that will be used to upload test cases on a source code repository. Authentication by login/password remains available.
Improved administration and management of Xsquash4Jira synchronizations
Xsquash4Jira configuration is now taken into account in project templates
You can now configure the Xsquash4Jira plugin in a project's template.
When creating a project from a template, a new option allows to take the Xsquash4Jira configuration from the template to the project level. You can then choose to :
Link Xsquash4Jira project configuration with that of the template: the plugin's configuration is managed in the template, apart from the synchronizations. All changes made in the template will be reflected in the linked projects.
Not link Xsquash4Jira project configuration with that of the template: the plugin's configuration in the project can evolve independently from that of the template. The changes made in the template will not affect the Xsquash4Jira configuration of the projects linked to the template.
Simulate an Xsquash4Jira synchronization before adding it
A new option to simulate an Xsquash4Jira synchronization before adding it is available. It allows you to view the number and details of the tickets it contains to make sure that they correspond to the perimeter to sync.
In the requirements library, the synchronization status of the linked Jira issue is displayed
In the requirements library, a new icon next to every synced requirement shows the synchronization status of the linked Jira issue.
The icon's color indicates whether the Jira issue is still synced, unsynced (because it no longer fits into the synchronization perimeter), or deleted or moved in Jira. This information is also available in a requirement's information.
This color code also applies to synchronization folders. It allows you to see quickly if the synchronization is in success, failed, or if it contains issues that are no longer synced.
BDD test cases are taken into account in editable test books
From now on, BDD test cases are taken into account in editable test books.
