Skip to content

Squash TM 8.X Release Notes

Automated Tests with Squash Orchestrator

  • Updating Squash TM to version 8.X also requires updating Squash Orchestrator to version 4.14.
  • The execution of automated tests from Squash TM uses temporary API tokens. Therefore, the property squash.rest-api.jwt.secret is required to run automated tests with Squash Orchestrator from Squash TM.

Squash TM 8.0.0

Released on October 29, 2024

Evolutions

  • Requirements:

    • Display of the number of test cases associated with standard requirements in the "Standard Requirements Linked to This High-Level Requirement" table of a high-level requirement

  • Test Cases:

    • Addition of a link to navigate to a requirement associated with a test step

  • Executions:

    • Renaming of the Campaign workspace to Execution workspace.
    • Addition of new objects, "Sprint" and "Sprint Group," in the Execution workspace to validate requirements in a sprint-based approach:
      • Creation and organization of sprints in the hierarchy
      • Management of sprint content
      • Testing and validation of sprint requirements
      • Management of sprint status
    • Synchronization of GitLab milestones/iterations and Jira sprints into Squash sprints

  • Automated Executions:

    • Real-time visualization of execution logs
    • Availability of the execution log file, updated at a defined frequency
    • Display of execution duration for automated tests
    • Monitoring of execution environment availability and orchestrator status

  • Xsquash4GitLab / Xsquash4Jira:

    • Initial configuration and modification of sprint synchronization in the Execution workspace
    • Display revamp of the synchronization table on the plugin configuration page
    • Mandatory simulation before adding or modifying a synchronization

  • Administration:

    • Addition of a user profile management workspace:
      • Creation of user profiles with customized permissions in the administration workspace
      • Activation/deactivation of a user profile
      • View of users and teams associated with a profile
      • Display of the permissions matrix by profiles
    • Import of Xray projects into a Squash project (test cases and execution plans)
    • Tracking of planned and completed Xray imports
    • Improvements for source code management servers:
      • Simplified repository addition window
      • Option not to transmit credentials to execution environments
    • Creation of an API token by an administrator on behalf of a "Test Automation Server" type user

  • SAML:

    • Addition of a property to prevent users from authenticating to Squash with their Squash credentials

  • Technical:

    • Addition of a property to define the location on the server where Git repositories are cloned for transmitting Gherkin or BDD test cases defined in Squash TM
    • Addition of a property to limit the maximum number of requirements to import per import file
    • Addition of a property to limit the maximum number of tickets a Xsquash4GitLab or Xsquash4Jira synchronization can contain when added
    • Integration of certain plugins into Squash TM:
      • Action Words Library
      • Result Publisher
      • Squash AUTOM
      • Test Plan Retriever

  • Performance improvements:

    • Test case import
    • 217 Display of the Execution workspace screens
    • 214 Display of a campaign dashboard containing charts
    • Display of the iteration test plan grid
    • Launch of large iteration test plans
    • Display of the list of known issues
    • Deletion of multiple projects
    • …

  • License:

    • Addition of custom templates management used for editable reports to Community version

  • REST API:

    • Security :
      • Removal of technical details and stack traces from responses
    • Depreciations :
      • Deprecation of /permissions endpoints in favor of /clearances, which now support custom profiles. No removal date has been set, but no future enhancements will be made to /permissions.
    • Transverse :
      • Integration of Action Word Workspace API endpoints into the new Action Words menu
      • Get sprint group (/sprint-groups/{id}): simplified retrieval of sprint group information
      • Get sprint (/sprint/{id}): simplified retrieval of sprint information
      • URL standardization for retrieving a campaign by name:
        • Old endpoint: /campaignsByName/{name}
        • New endpoint: /campaigns?campaignName={name}, for example: /campaigns?campaignName=MyCampaign
      • Get automated execution extender (/automated-execution-extenders/{id}): addition of execution time (duration) in execution information
      • Get a synchronized requirement (/requirements/{id}): addition of ID (remote_req_id), URL (remote_req_url), and perimeter status (remote_req_perimeter_status)
      • Get progress status (progress_status) for a campaign, iteration, and test suite
      • Get, add, and modify an iteration’s status (status)
      • Get, add, and delete an API token (/tokens)

  • Administration REST API:

    • Management by Squash TM of the local path (repository_path) for source code management servers
    • Generation of an API token for users of test automation servers (/users/{id}/tokens)
    • Locking of user modification (/users/{id}) between the User and Test Automation Server groups
    • Continuation of integrating classic REST API documentation related to administration into the REST API administration documentation

Corrections

  • Executions:

    • 189 The deletion of a folder in the Execution workspace, while a milestone was associated to the project, resulted in an error.
    • "Skipped" or "Cancelled" statuses were improperly displayed among the execution status list when this one should have excluded the automated execution statuses.
    • It was possible to resume an existing execution even if milestone was locked.
    • It was possible to try to add an issue to a deleted test case (this resulted in an error).

  • Reporting:

    • 209 Generating an editable requirement report with a "Select a milestone" selection and the "Print only the latest requirement version" box unchecked was failing with an error.

  • GitLab / Jira synchronization:

    • 277 Two synchronizations could target the same folder, resulting in the synchronization running the last failing.
    • A never-run synchronization was reported as being run last on January 1st, 1970.
    • If a GitLab synchronization was configured with a target path containing a space at the beginning of one of its components, a new folder was created for each milestone.
    • It was possible to declare two Jira synchronizations with the names differing only by prefixed spaces.

  • Automation:

    • Filtering the automated suite view was broken.
    • 239 On a PostgresSQL database, filtering on the "SCM URL" column from the automation space (autom.) generated an error.
    • 13 If automated tests were reordered in a test plan, their results in the executions details dialog were incorrectly sorted.
    • In the Automation workspace, trying to transmit a test case already transmitted resulted in an error, while this should have no effect.
    • The statuses of the execution of an automated test and of its test suite were not properly respectively set to "Blocked" and "Error" in the case of a technical error.
    • When a test suite containing tests from several projects is launched, several workflows are created. Killing one of them was not properly handled: it was cancelled, but the results of the tests of the other workflows were not updated in the test suite view.
    • Running some tests from a test suite using Squash TF was broken: the launch generated an error.
    • Test cases, in a project configured with an automation server and included in a test plan of a project with no automation server, had improperly managed executions.
    • Reports of automated tests having a slash in their title could not be displayed.
    • The verification of the killswitch URL was failing sometimes, e.g. when going through a reverse-proxy, while the URL was correct.
    • Some additional orchestrator configurations that were invalid YAML were not reported as such.

  • Administration:

    • 103 Sorting of the profiles in the clearance table was wrong.

  • Cross-Functional:

    • Trying to import a file larger that the configured limit resulted in an internal error rather that displaying an error message.
    • When searching requirements or test cases on the respective search page, using a string containing multiple spaces or an ending space, resulted in an error on Squash TM instances using a PostgreSQL database.
    • Squash TM would not start if a bugtracker plugin was removed while the bugtracker was still configured.
    • The personal tokens were not properly sorted in the token view.

  • Ergonomics:

    • In the attachment preview, an empty tar file was displayed with no indication that it was empty.
    • The menu for accessing the REST API documentation was not displayed if there was yet no project in Squash TM.
    • Clicking on a link in a rich text resulted in the text filed switching into edit mode.
    • Disabled checkboxes and dropdown lists were improperly rendered.
    • When the search preload is deactivated, a message now clearly indicates if the search has not been run yet or if the search has been run and returned no results.
    • Dragging an action in the Action word workspace used to wrongly trigger the highlight of the text beneath it.
    • A "Next" button was badly positioned.
    • Some grids were not scrollable horizontally when using a trackpad.

  • Security:

    • Improved control on files downloadable from Squash TM;
    • Improved control of the RBAC when accessing the backend API.

  • Xsquash4Jira:

    • There was no dialog asking the user what should be done with the existing synchronizations (delete them or keep them) when s/he disabled the Xsquash4Jira plugin.

  • Xsquash4Gitlab:

    • 241 In some peculiar cases, such as modifying the configuration of the Xsquash4Gitlab plugin in two different Browser tabs, some "ghost" lines (i.e., lines with an undefined GitLab field) in the field mappings.

  • GitLab Bugtracker:

    • The preview of GitLab issues did not properly handle HTML special characters.
    • Missing user GitLab credentials were not properly handled when configuring the GitLab Bugtracker plugin. The plugin now explicitly asks the user to provide his/her credentials.

Compatibility with third-party softwares

Squash TM version 8.x has been validated with the following versions of thir-party softwares. It should be compatible with more recent versions.

Ticket management

Software Version
GitLab Cloud 17.6.0-pre
GitLab Server 16.8
Jira Cloud 10.01
Jira DataCenter 9.11.2

Anomaly management

Software Version
Azure DevOps 2022.1
Bugzilla 5.0
Mantis 2.25.3
Redmine 5.1.3
RTC 6.0.3
Tuleap 14.4.99.130

Automating

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