SquashTM 13.X Release Notes

SquashTM 13.0.1

Released on 2/16/2026

Corrections

• Executions:

  • The execution order of test plans was reversed after deleting a test suite or an automated suite.

• Technical:

  • Slowdowns could occur during database upgrade when dropping foreign keys around the table AI_USE (former AI_USAGE).

SquashTM 13.0.0

Released on 1/28/2026

Evolutions

• Automation:

  • Assistance in selecting test cases to automate: add "My latest analysis" mode.
  • Assistance in selecting test cases to automate: improved ergonomics (new grid columns, improved project filtering…).
  • Automated execution supervision: progress bar displays executions pending retry with a different color.
  • Clean up automated suites: remove orphaned failure details.

• Artificial Intelligence:

  • AI-powered test case generation, available with the SquashTM Ultimate offering, is now generally available.
  • The generation context has been enriched with requirement metadata (title, type, category, criticality) as well as images embedded in the requirement description, for supported models.
  • The configuration of Artificial Intelligence servers has been redesigned. It now offers a simplified configuration for mainstream providers (OpenAI, Anthropic, Mistral AI…) and a custom configuration supporting a wider range of APIs. This mechanism provides a sustainable foundation for future AI features in SquashTM.

• Transverse / Ergonomics:

  • The date and time formats have been made consistent in all languages.

• REST API:

  • The REST API is now stateless.
  • Update test suite names via the API.

• Administration:

  • Admin recycle bin: "Administrator" and "project leader" profiles can now restore and permanently delete test cases.

• Technical:

  • Streaming of campaign exports, including custom export.

• Tuleap Bugtracker:

  • 566 Allow token authentication.

• Redmine Bugtracker:

  • 140 Add autocompletion on 'Assignee' and 'Target version' fields.
  • 541 Clarify error message formatting.

Corrections

• Executions:

  • Data cleaning: orphaned executions are now removed during upgrade.
  • Import executions: empty mandatory values (like custom field value or attachment name) were not processed correctly.

• Reporting:

  • Campaign custom export: the filling of test steps by any type of custom field was not reported.
  • Qualitative progress:
    • The preview was truncated before download.
    • The "Requirement list with associated execution status" tab failed to load when the "settled" status was enabled.
  • Test case report (editable format): requirements linked to a test step were not listed.
  • Requirement report (editable format): the high-level requirement link did not appear.
  • Custom charts with execution plan items fields were not displayed under some circumstances.

• Test Cases:

  • The feature "Create test cases from copied requirements" was failing in a specific case.

• Automation:

  • 579 The deletion of automated suites was failing.

• Import:

  • 474 Both the simulation and the post-import report indicated warning messages about test steps even though the TC_STEP_NUM column was correctly populated and their import was successful.
  • The XLS import of test cases did not handle the link with requirements properly.

• REST API:

  • 556 The access to the REST API documentation is now possible without any authentication (AD, OpenID-Connect, LDAP)
  • If a requirement version or a test case were associated with several milestones, then the API request /api/rest/latest/{entity Rel Name} did not return the correct number of results.
  • 581 The number of results returned by the API request /api/rest/latest/projects was incorrect when projects were associated with multiple milestones.

• Authentication:

  • SAML:

    • The authentication was partial whereas the assertion validation was failing.

• Bugzilla Bugtracker:

  • 523 SquashTM could not connect to a Bugzilla instance over HTTPS when declaring the bugtracker server.

• Xsquash4Jira:

  • 533 Links between classic requirements and high-level requirements were not automatically created during the initial synchronization.

• Jira Cloud Bugtracker:

  • The bug reporting form initialization could time out.

• Jira Automation Workflow:

  • Plugin configuration page: fetching available projects is faster.

• Tuleap Bugtracker:

  • PNG and docx files were not inserted when reporting a new issue from SquashTM.

• Redmine Bugtracker:

  • 549 Locked or closed versions were displayed and selectable in Version custom fields.
  • 551 Validation error messages on numeric fields didn't specify which field was causing the error.

• Performance:

  • 515 The test case deletion was excessively slow.
  • 528 Optimization of the display time of the automated suites.
  • Improvement of performance upon the deletion of a folder.
  • Optimization of the display time of a folder or a library.
  • Optimization of the display time of statistics.

• Administration:

  • It was not possible to create a rich text type custom field when an image was set as the default value.
  • Modifying inactive users with API was making them active.

• Transverse:

  • 391 Dropdown lists were not anchored to select field after a scroll in issue reporting dialog.

• Configuration file:

  • The property squash.security.api-session.max-concurrent-sessions that was removed in SquashTM v.10.2.7 was still documented in the default configuration file.

Compatibility with third-party software

Ticket management

Anomaly management

Automation