Skip to content

SquashTM 12.X Release Notes

Docker Image: Version upgrade

Attention: To migrate from SquashTM 8.1.X (or earlier) to SquashTM 12.0.0, you must go through the intermediate version SquashTM 9.0.X. Direct upgrade is not supported. See further information on version upgrades.

Automated tests with SquashTM Orchestrator

When upgrading SquashTM to version 12.X, it is strongly recommended to also upgrade SquashTM Orchestrator to version 6.1. Otherwise, inconsistencies in execution statuses may occur.

SquashTM 12.0.2

Released on 11/20/2025

Corrections

  • Bugzilla Bugtracker:

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

  • Redmine Bugtracker:

    • 532 Reporting an issue from SquashTM to Redmine failed if an anonymous user group was present on Redmine.

SquashTM 12.0.1

Released on 11/07/2025

Corrections

  • Transverse:

    • 522 It is now possible to export up to 1000 items with large IDs from a search page (requirements and test cases).

  • GitLab BT:

    • Fix early termination of GitLab bugtracker cache construction.

SquashTM 12.0.0

Released on 10/29/2025

Evolutions

  • Automation:

    • A new "DevOps" mode simplifies the reporting and consolidation of automated test results executed in a CI/CD pipeline directly into an iteration.

      • New API endpoint: POST /import/results/{iteration_id} (see specification).
      • Automatic matching via the "automated test reference" field. The free-form format of the field allows adaptation to the technology of the executed tests.
      • For each test, the mechanism allows importing:
        • the test status;
        • the test execution duration;
        • error assertion messages;
        • execution attachments;
        • execution custom fields.

    • Automatic retry of failed tests for flaky automated tests and when triggering test execution from the repository (autonomous mode). Each retry is recorded and creates, if applicable, a new "execution" in the test plan and automated suite.

    • Improved performance and user experience when using intelligent prioritization assistance for test cases to automate.

  • Executions:

    • Improved traceability of user actions:

      • two distinct columns are now displayed in execution plans to better distinguish roles:
        • The "Assigned" column indicates the person to whom the test case has been assigned;
        • The "Executed by" column displays the login of the user who performed the execution.
      • in the "Test cases verifying this requirement" block, the date and time of the last execution are now displayed in addition to the associated status.

    • Continued alignment of sprints and sprint groups with other entities in the Executions space.

      • Column display in a sprint execution plan is now configurable.
      • The search result in the test cases space includes a new "Number of sprints" column similar to the "Number of iterations" and "Number of executions" columns.
      • Test case search results are filterable by the number of sprints they are associated with.
      • The "Test status", "Success/failure rate", and "Importance of never-executed tests" charts in the dashboard are now clickable. Each click redirects to the search page with results automatically filtered according to the selected portion, for both sprints and sprint groups.
      • New charts are available on sprint groups, mirroring those of individual sprints. They consolidate group data for an overview of progress:
        • Requirements validation status;
        • Criticality of unvalidated requirements;
        • Test case coverage;
        • Test status;
        • Success/failure rate;
        • Importance of never-executed tests.

    • It is possible to restart a sprint or iteration execution deleting the history.

  • Transverse / Ergonomics:

    • The issue reporting form for the Redmine bugtracker now loads faster thanks to the implementation of a caching system.

  • REST API:

    • 429 It is now possible to target entities linked to milestones (projects, requirement versions, test cases, campaigns) using a new filter on existing associated endpoints. These filters can be applied:

      • On endpoints at the SquashTM instance level (across all projects);
      • On associated sub-endpoints of a specific project;
      • Filtering is done by label or milestone identifier.

    • The REST API has been enriched to allow complete management of sprints and sprint groups via associated endpoints

      • Reading the content (Folders, Sprint and sprint groups) of a sprint group;
      • Adding, reading, updating and deleting sprint requirements;
      • Adding, reading, updating and deleting the execution plan of a sprint requirement;
      • Reading issues linked to a sprint;
      • Reading issues linked to a sprint requirement.

  • Technical:

    • Version upgrade to Spring Boot 3.5.4 and management of related deprecations.
    • Version upgrade to Angular 20 and management of related deprecations.

Feature removals

  • The database upgrade mechanism specific to the Docker image has been removed in favor of the generic mechanism embedded in SquashTM since version 9.0.0. To migrate from SquashTM 8.1.X (or earlier), deployed via the Docker image, to SquashTM 12.0.0, you must go through the intermediate version SquashTM 9.0.X. Direct upgrade is not supported.

Corrections

  • Executions:

    • The link that directs the user to the execution folder from the execution search is now fixed.
    • During an exploratory test session, the "assigned" column is only filled in once notes have been entered.
    • The issue causing the test status label to update despite disabling 'Synchronization of the test status monitoring' has been fixed.
    • The tooltip for the button that allows displaying only the latest executions has been modified for better clarity.
    • It is now possible to execute a sprint test plan item from the test plan items search page.
    • The execution button now displays correctly again when adding a new requirement to sprint requirements.
    • The execution button now remains visible after a page refresh with a column configuration.
    • Results now display correctly when the "Last executed item" option is used with a sprint group as the scope.
    • The execution button is no longer accessible for a test plan item associated with a deleted test case.
    • Filters are now correctly reset when the "link to a requirement" column is hidden along with another column.
    • The message displayed when performing the "Restart with history deletion" action has been corrected to match the sprint context.
    • The display of issues associated with all objects in a folder, as well as the number of issues in the anchor, now works correctly.
    • The display of requirements with Minor and Critical criticality in the "Criticality of unvalidated requirements" chart on the execution dashboard is now correct.
    • Folder deletion could fail.
    • The #EXECUTIONS, #_ISSUES, and EXEC_STEP#_#ISSUES columns of the complete campaign export displayed incorrect results.
    • 292 The display of information in the iteration test plan items grid was partially incorrect after updating the script to version 7.0.4.

  • Reporting:

    • Generating custom charts from a "Custom field" attribute was impossible.
    • In the qualitative progress report, the sum of requirements linked to a test case present in a campaign was no longer counted correctly.
    • Test cases and Requirement books (PDF and editable versions) as well as the qualitative progress report did not take into account the "Project" filter when a milestone was selected as scope.
    • Several fixes have been made to multi-campaign and iteration reports. These fixes are mainly ergonomic, related to custom fields or authentication.
    • Creating certain execution progress reports required excessively long execution time.
    • Fixed a display error in the ordering of custom fields.
    • "Tag" type custom fields were not reported in the Test cases book (editable version). The absence of "tag" type custom fields also impacted the Requirements book.
    • Generating the requirements coverage report from a milestone failed to indicate the name of the selected milestone. The issue also appeared in the Requirements book.
    • The scope defined by a milestone was not respected: requirements not associated with this milestone appeared in the Requirements book.
    • 31 Chronological order was not respected in a custom chart.
    • 511 The cumulative progress chart displayed the viewing window two hours ahead of the defined start date, thus shifting the iteration name.

  • Requirements:

    • 407 It was no longer possible to associate or dissociate a milestone from a requirement with "approved" status.
    • Modifying a custom field of a requirement with "approved" or "obsolete" status is now blocked.
    • The print window for a requirement is no longer blocked when there is an empty "tag" type custom field.

  • Test Cases:

    • The tooltip on the execution plan type column has been added.

  • Automation:

    • Robustness improvements for publishing execution results.
    • 250 The order was not constant for automated executions in the monitoring dialog and test plan.
    • Dataset parameters did not follow inheritance rules.
    • UX improvements for test case automation selection assistance.
    • An analysis could remain stuck in the test case automation selection assistance with MariaDB 11.
    • Launching tests with SquashTF resulted in an Http 403 Forbidden error.
    • Updating execution statuses with Jenkins and MariaDB 11 failed.
    • Improved HTML report layout in preview.

  • Import:

    • 464 The error occurring during a CTE query for retrieving a test case path has been fixed.
    • 492 Test case links are now correctly imported for synchronized requirements.
    • The import of links between requirements and test cases is now complete, even when a requirement has multiple associations.
    • Labels of type ITERATION_TEST_PLAN_ITEM are now imported with an empty string instead of a null value.
    • Interoperability failed at the parameter format level for importing Xray data.

  • Export:

    • The "Number of iterations" and "Number of called test cases" columns now display correct data during export. Additionally, the "Number of sprints" column is now included in the export.
    • Test case export failed when using the "All fields" option from search results.

  • Artificial intelligence servers:

    • Error logging for AI test case generation now captures complete responses from providers.

  • Transverse:

    • A modification of the STRING_CONTENT column type in the ATTACHMENT_CONTENT table blocked the update of certain instances.
    • Fixed dropdown list positioning after scrolling.

  • Redmine Bugtracker:

    • 362 It was impossible to report an issue on a private project when authenticating by Token.

  • Xsquash4Jira:

    • 501 Pagination when adding synchronization for more than 50 tickets in Xsquash4Jira now works correctly.
    • 502 Residual calls to the /search endpoint when reporting from SquashTM to Jira have been removed.
    • 503 POST requests to the /search/jql endpoint in Xsquash4Jira are now executed correctly.
    • Loading the campaign assistant from a Jira ticket is now operational in Xsquash4Jira.
    • Sprint synchronizations failed when the “Sprint” field was empty in Jira.

  • Jira Cloud BT:

    • POST requests to the /search/jql endpoint in Jira Cloud BT were failing. They are now executed correctly.

  • Xsquash4GitLab:

    • The "Force synchronization" button now applies correctly to synchronized tickets in a sprint in Xsquash4GitLab.
    • Modifying the reference of a sprint requirement synchronized with GitLab is now supported in Xsquash4GitLab.
    • A GraphQL query complexity error was preventing the publication/update of notes.

  • Performance:

    • Downloading the execution progress report experienced significant degradation.
    • The test case creation feature from requirements had degraded execution time.
    • Generating the complete campaign export was no longer instantaneous.
    • Improved performance for copy/paste of entities in Requirements and Test Cases spaces.

  • Administration:

    • 485 When changing project template, all values are now correctly populated.
    • Fixed display of an error message that was incorrectly displayed multiple times.
    • The list of projects to associate is now sorted alphabetically.
    • Modified the information message when deleting an artificial intelligence server and corrected typographical errors.
    • Aligned the ergonomics of the artificial intelligence server configuration page with those of other server types.

Plugins

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

Compatibility with third-party software

SquashTM version 12.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 10.4.1

Anomaly management

Software Version
Azure DevOps Services 2025.01
Azure DevOps Server 2022.1
Bugzilla 5.2
GitLab Cloud 18.5.0-pre
GitLab Server 17.7
Jira Cloud 10.01
Jira DataCenter 10.4.1
Mantis 2.25.3
Redmine 6.0.6
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