Skip to content

Squash TM 11.X Release Notes

Removal of old files from the report plugins

Files from the PDF and Editable Requirements Report, PDF and Editable Test Case Report, and Qualitative Progress plugins are no longer included in Squash TM distributions. These plugins are now integrated into the core of Squash TM.
The old versions of the files of these plugins must be removed from the squash-tm/plugins directory, as this could cause side effects and prevent proper startup of Squash TM.

Free disk space necessary for the database upgrade

For users having a MariaDB database containing a lot of attachments, care should be taken to have enough free disk space: as described here, the database should consume less than 40% of the disk space, otherwise the upgrade to Squash TM 11.0.0 may fail. If your MariaDB database is larger than 40%, you need to allocate more disk space.

Change in Spring Boot Actuator configuration properties

Squash TM now runs on Spring Boot 3.4.5 and incorporates changes to accommodate deprecated configuration properties.

The following property has been deprecated: management.endpoints.enabled-by-default.

It is now replaced by: management.endpoints.access.default.

This change provides more fine-grained control over access rights to the Actuators web endpoints. The new property lets you define the default access level for actuator endpoints: none, read-only, or unrestricted. For more information about monitoring SquashTM, see Supervise Squash TM.

End of H2 DBMS support

The H2 DBMS is no longer supported. Users wishing to easily discover Squash TM can do so by using the Docker image or our trial offerings.

Campaign and iteration report - Template report changes

The default report templates have been updated to support multiple selection in the perimeter.

If you are using custom templates, make sure to update them accordingly.

Warning: legacy templates will no longer be supported starting with Squash TM 15.

Renaming of the "Test automation server" group

The user group "Test automation server" has been renamed "Technical account".

Squash TM 11.0.5

Released on 11/19/2025

Corrections

  • Xsquash4Gitlab:

    • A GraphQL query complexity error was preventing the publication/update of notes.

  • Bugtracker Bugzilla:

    • 523 SquashTM was unable to reach a Bugzilla instance over HTTPS when declaring the bugtracker server.

Squash TM 11.0.4

Released on 09/23/2025

Corrections

  • Charts:

    • Some charts containing custom fields could not be displayed.

  • Jira Cloud

    • Xsquash4Jira:

      • 502 A remaining /search call was still used when reporting from Squash to Jira Cloud.
      • 501 Synchronization requiring multiple batches (whose size is defined by plugin.synchronisation.jira.batchSize) could terminate prematurely after the first batch.

    • Xsquash4Jira, Jira Bugtracker (Cloud) & Jira Automation Workflow:

      • 503 POST requests with /search/jql could fail in some cases.

  • Reports:

    • Creating certain execution progress reports required an excessively long execution time.

  • REST API:

    • The new squash.security.api-session.max-concurrent-sessions parameter introduced in 11.0.2 was not working correctly. It has been removed. A more robust solution will be introduced in a future version of Squash TM.

Squash TM 11.0.3

Released on 09/18/2025

Packaging

  • Fixed the Xsquash4Jira version included in the plugins folder: it is now correctly set to 11.0.2 instead of 11.0.1.

Squash TM 11.0.2

Released on 09/16/2025

Evolutions

  • REST API:

    • A new squash.security.api-session.max-concurrent-sessions parameter allows limiting the number of simultaneous sessions that a given user can have with the REST API.
    • The login of the user making a REST API call is now recorded in the log file.
    • REST API calls referencing a non-existent id no longer generate stack traces in the log file.

  • GitLab Bugtracker:

    • "debug" level logs detailing the cache loading phases have been added to facilitate problem analysis during cache initialization.

Corrections

  • Azure DevOps Bugtracker:

    • 488 The bug report form was empty when reporting a new issue.

  • Xsquash4GitLab:

    • 483 The Publish progress status as a GitLab label option was unavailable when using a project template.

  • Xsquash4Jira, Jira Bugtracker (Cloud) & Jira Automation Workflow:

    • 495 Update SearchClient after Jira Cloud API /search endpoint removal
    • 482 Update following the deprecation of the Jira Cloud API /search endpoint.

Squash TM 11.0.1

Released on 08/21/2025

Corrections

  • Test Cases:

    • The import of test cases could fail when the database contained a very large number of test case calls.

  • Technical:

    • The tm-10.0.0-migrate-iteration-executions changeset included in the 10.0.0 upgrade script could cause the database update to fail.
    • The configuration file did not include the squash.control.deletion.threshold property (see the "documentation").

  • REST API:

    • The REST API documentation for GET Sprint Requirement Version incorrectly stated that certain fields were null in NATIVE mode.

Squash TM 11.0.0

Released on 07/30/2025

Evolutions

  • Requirements:

    • External requirement repositories serve as the source of truth for synchronized requirements.
      • 283 Requirements with "approved" or "obsolete" status are synchronized;
      • As a synchronized field, the "status" field cannot be modified directly in Squash. This field is updated with each synchronization.
    • To display test status directly, GitLab labels are automatically published on issues linked to synchronized requirements, enabling rapid visual identification of test progress states.

  • Executions:

    • Sprint alignment with other objects in the executions space.
      • Executions performed through a sprint are now included in the search results within the Executions workspace.
      • A new "dashboard" anchor provides visual tracking of sprint validation progress. It is possible to limit to the status of the latest execution through a filter.
      • Executions can be chained from the general test plan of a sprint, as well as from the test plan of a sprint requirement.

  • Reporting:

    • Tests executed across multiple campaigns and iterations can be consolidated into a single document.
      • 295 Generation of multi-campaign and multi-iteration reports;
      • Customization of multi-campaign and multi-iteration report templates.

  • Automation:

    • Intelligent test case prioritization assistance through automated analysis based on execution frequency, success rate, and business criticality.
      • Test asset analysis using an algorithm to suggest the best automation candidates;
      • Visualization of the latest analysis (in progress or completed) for the connected user;
      • Validation or rejection of suggested automation candidates;
      • Visualization of tests eligible for automation.
    • 29 Capability to transfer datasets from a called test case to automated scripts executed by the orchestrator (autonomous mode).

  • Transverse / Ergonomics:

    • 424 Secured deletion with the addition of a confirmation request before deletion. The user explicitly specifies, in a popup, the number of elements they will delete.
    • Project deletion assistance with localization of residual elements.
    • 423 Enhanced webhook processing performance through the implementation of targeted GraphQL queries. Webhooks are processed immediately after completion of individual synchronizations, rather than waiting for the end of the complete synchronization cycle.
    • The "Test automation server" user group has been renamed to "Technical account" in order to better reflect its broader purpose.

  • Administration:

    • Automation space permissions are configurable for custom profiles.

  • REST API:

    • Creation of API endpoints for sprint management.
      • Creation, reading, modification, and deletion of a sprint group;
      • Creation, reading, modification, and deletion of a manual sprint.

  • Performance:

    • Display of elements in the inter-project library.
    • Display of an iteration's execution plan.

  • Technical:

    • Migration of five reporting plugins into the core:

      • report.books.requirements.editable-X.Y.Z.RELEASE.jar
      • report.books.testcases.editable-X.Y.Z.RELEASE.jar
      • report.books.requirements.pdf-X.Y.Z.RELEASE.jar
      • report.books.testcases.pdf-X.Y.Z.RELEASE.jar
      • report.qualitativecoverage-X.Y.Z.RELEASE.jar

    • Configuration and startup of Docker image via Spring environment variables.

    • Version upgrade to Spring Boot 3.4.5 and management of related deprecations.
    • Version upgrade to Angular 19 and management of related deprecations.

Feature removals

  • The RTC Bugtracker plugin is dropped and is no longer distributed from Squash TM 11.0.0.
  • The H2 DBMS is no longer supported.

Corrections

  • Executions:

    • 411 Images were not displayed during execution if the test case belonged to a project without authorization.
    • Test cases attachments were not updated once the test case was executed.
    • The "result" block of an execution scenario step contained an unwanted empty white space.
    • The progress statistics anchor was not automatically updated in certain cases.
    • The number of test cases in the "statistics" anchor of a test suite was incorrect.
    • The test plan content was not copied when an existing suite is copy pasted in another iteration.
    • Information and error messages during chained execution of a test plan containing an exploratory test were misleading.
    • Executing a test case from the "play" button at the end of the line was impossible in an iteration.
    • CSV campaign exports were using a comma as a separator instead of a semi-colon and rich text CUFs were not properly escaped.

  • Reporting:

    • 100 Execution reports contained incorrectly encoded characters on content synchronized from Jira.
    • 246 Complete campaign export omitted test steps that contained a called test case.
    • 361 It was impossible to correctly open a report containing emoticons in a simple field.
    • Generation of a campaign report and an iteration report was impossible when the option to include anomaly details was checked.
    • Generation of the execution progress report for a campaign linked to a milestone was impossible.
    • Campaign export was inconsistent regarding date formats and test step identifiers.
    • Test case import was impossible for certain test case names, example: "$/".

  • Requirements:

    • Deletion of a requirement covered by multiple test cases resulted in an error.

  • Test Cases:

    • Images in a test case description were not displayed when the test case was created from a requirement via copy/import.

  • Automation:

    • 451 It was impossible to activate the automation workflow when an automatic script was already defined in the project.
    • Filtering by date in the "transmitted on" column of the assignment table in the automation engineer view of the automation space was impossible.

  • Import:

    • 438 During import, adding a dataset to a test case failed.

  • Artificial intelligence servers:

    • 461 The artificial intelligence server configuration validation failed due to a 201 response code returned by the provider’s API.

  • Transverse:

    • The number of requirements in the project dashboard was incorrect.
    • The URL of images pasted in rich text areas was incorrect.
    • Column configuration on the search page when automatic search launch for all search pages across different spaces was enabled caused redundant queries.
    • Adding an attachment exceeding 15 MB in size was not possible.
    • UTM parameters were missing for "de" and "es" documentation.
    • Deletion of a project containing an action word library was impossible without a license.
    • Search was automatically executed when a search criterion was deselected.
    • Sorting on the "status" column of profiles in the administration space was reversed.

  • Azure DevOps Bugtracker:

    • 419 Some HTML tags were displayed in the description of tickets to be linked.

  • Xsquash4Jira:

    • 436 The "Sprint" field was not retrievable from Jira Cloud.
    • Dissociation of a US from an epic in a "team-managed" Jira project was not reflected in Squash TM.

  • Xsquash4GitLab:

    • The error message was not displayed below mandatory fields in the "add synchronization" popup.

  • REST API:

    • It was not possible to create a high-level requirement.
    • Clarification provided on type and cause in case of error on a field value in a POST request.
    • The field name was missing when returning a validation error (fieldValidationError) following a POST call on /ai-server.
    • Validation of the "parent" node during a patch call was not necessary and could result in 500 errors.

  • Performance:

    • Deadlocks were possible due to non-deterministic entity locking order when multiple threads attempted to lock the same entities in batches.
    • Deletion of an element from the execution plan, when it included more than 1000 automated suites, could cause a timeout, resulting in an HTTP 502 error.

Plugins

  • New version for all plugins: compatibility with Squash TM and fixes.
  • Plugin release notes are included in the Squash TM release note.

Compatibility with third-party software

Squash TM version 11.0.0 has been validated with the following versions of third-party software. It should be compatible with more recent versions.

Ticket management

Software Version
GitLab Cloud 18.3.0-pre
GitLab Server 17.7
Jira Cloud 10.01
Jira DataCenter 9.11 & 10.4.1

Anomaly management

Software Version
Azure DevOps Services 2025.01
Azure DevOps Server 2022.1
Bugzilla 5.0.6
GitLab Cloud 18.3.0-pre
GitLab Server 17.7
Jira Cloud 10.01
Jira DataCenter 10.4.1
Mantis 2.25.3
Redmine 6.0.2
RTC 6.0.3
Tuleap 14.4.99.130

Automation

Testing technologies Version
Agilitest 💎 2.3.0
Cucumber JVM 7.0.0
Cucumber JVM 4.2.6
Cypress 12.12.0
JUnit 5.3.2
JUnit 4.12
Katalon 💎 8.2.0
Playwright 1.43.1
Postman 8.12.1
Ranorex 💎 9.5
Robot Framework 6.1.1
SKF 1.14.0
SoapUI 5.6.0
UFT 💎 15.0.2