The version 5.0 of Squash TM is available for download.
This version includes the following features:
Management of Jira epics in Squash TM
Elaboration of execution plans from a scope of GitLab issues
Custom export from a multiple selection of campaigns and iterations
Enable/disable deletion of objects from libraries customizable by users
Improvements in Robot Framework scripts generated by Squash from BDD test cases
New simple Squash automation workflow
Evolutions on environment variables (automation)
Display of the location of objects on their consultation page
Ergonomic evolutions and bug fixes
Discover the main new features of Squash TM 5.0 below.
For the complete list of evolutions and fixes, you can consult the release note of the version.
Management of Jira epics in Squash TM
Requires the Squash TM Premium plugin, included with the Squash TM Premium offer.
Jira epics are now managed in Squash TM in order to bring to users an overview of a macro-feature in an agile context.
For this purpose, epics and epic-user story links are synchronized in Squash TM respectively into high level requirements and high level requirements-standard requirements links.
Links can be made between elements from different synchronizations, making several types of organization possible (epics and user stories in the same Squash TM folder, in different folders, in different projects).
For existing synchronizations, no additional settings are required, the already synchronized epics are automatically converted into high-level requirements and the links are retrieved.
To make it easier to organize execution plans by major features, the Xsquas4Jira execution plan designer allows you to automatically create test suites for each epic with the tests that directly verify the epic or its user stories.
Elaboration of execution plans from a scope of GitLab issues
Squash TM 5.0 reinforces the integration with GitLab by facilitating the elaboration of execution plans in order to validate an increment delivered by the team.
To do so, a wizard automatically identifies test cases covering a set of GitLab issues that meet user-defined criteria. For example, all test cases covering an iteration or milestone defined in GitLab, or all test cases that verify bug fixes.
Custom export from a multiple selection of campaigns and iterations
From the Reporting Workspace, the custom export of campaigns can now be done from a multiple selection (several campaigns, iterations, tests suites, mixed selection, selected from potentially different projects).
Enable/disable deletion of objects from libraries customizable by users
Requires the Squash TM Premium plugin, included with the Squash TM Premium offer.
In order to avoid accidental deletions or simply to have more control over user permissions, it is now possible to grant, for each user, the possibility or not to delete objects in the libraries of the workspaces. This is reflected in the presence or absence of the delete button.
This setting applies only to user profiles that allow deletion and only to objects in the libraries of the various workspaces (requirements, test cases, campaigns, folders, etc.).
Improvements in Robot Framework scripts generated by Squash from BDD test cases
Various improvements have been made to the Robot Framework scripts generated automatically from BDD test cases in order to better comply with the Robot Framework standards and specificities.
New simple Squash automation workflow
Squash TM 5.0 offers a new automation workflow suitable for teams where the same person writes the test cases and implements the associated automated scripts.
It allows the user to indicate if the test case is eligible for automation, to link it to an automated script (manually or automatically by transmiting it to a git repository) and to mark it as automated, without leaving the Test Case Workspace.
Evolutions on environment variables
Squash TM 5.0 supports a new type of environment variables whose values can be interpreted by runtime environments.
Environment variables can now be associated directly to the project, it is no longer mandatory to associate them to the test automation server.
Display of the location of objects on their consultation page
The full path of the location of objects in the tree structure is now displayed from their consultation page.
