top of page

Delivery Squash 7.1, 7.2 and 2024-07 with API authentication by token and parallel jobs execution


This delivery contains the following features:


  • API authentication by token

  • Parallel jobs execution in Squash Orchestrator

  • Various improvements and bug fixes


The full list of new features and bug fixes is available on Squash TM 7.1, Squash TM 7.2 and Squash Orchestrator  2024-07 release notes.


API authentication by token

Squash API calls can now be made using tokens instead of requiring basic authentication (login/password).

These are personal tokens generated from the "My Account" page of each user.



These tokens inherit the user clearances but, depending on their usage and to prevent unintended operations, it is possible to define their permission level:


  • Read-only: allows only GET operations;

  • Read and write: allows all operations (GET, POST, DELETE, PATCH).



For now, these tokens are used only for direct calls to Squash APIs. Starting with Squash 8.0, they will also be used for displaying Squash data in Jira (Xsquash) and for executing automated tests with  Squash Orchestrator.


Basic authentication for the APIs still works but can be disabled, and it will no longer be supported after mid-2026.


Parallel jobs execution in Squash Orchestrator

Squash Orchestrator now allows parallel executions of multiple jobs. This speeds up automated tests execution since the jobs will be triggered as soon as an execution environment is available. They no longer need to wait for the previous job to finish executing, as long as no dependency is declared between them.


In order to avoid disrupting existing executions in case of undeclared dependencies, this parallelization is set by default to one job (meaning no parallel execution), but can be increased if needed. For more information, please see the documentation.

Comentários


bottom of page