Squash Orchestrator 4.8.0 Release Note

Introduction

Squash Orchestrator is a set of micro-services to perform automated test execution workflows described in a specific format.

This release note describes the changes of Squash Orchestrator version 4.8.0 compared to 4.7.0.

Squash Orchestrator 4.8.0 was released on December 18, 2023.

---

New features

• Issue orchestrator #390 Customization of the Postman launch command line from Squash TM
  Issue orchestrator #405 [Maven][Junit] Add more flexibility on junit plugin
  Issue orchestrator #442 Customization of the Robot Framework launch command line from Squash TM
  Issue orchestrator #443 Customization of the Cucumber launch command line from Squash TM
  Issue orchestrator #450 Customization of the Cypress launch command line from Squash TM
  It is now possible to specify additional options to add to an execution's command line through the {PROVIDER}_EXTRA_OPTIONS environment variable. This is currently available only for Robot Framework, Cucumber, Cypress, Postman, and JUnit. More details can be found on the page related to the implemented technology.

• Issue micronaut-java-plugins #21 🔑 [Publisher] Send tests statuses in real time to web application
  The publisher can now send test status in real time to Squash TM. This allows a user to see in the test execution overview popup the execution's progress. More details can be found here. This feature is available starting from Squash TM 6.0.

• Issue squash-orchestrator #128 🔑 Adapt squash-orchestrator image to java 17
  The squash-orchestrator image has been updated to use Java 17 instead of Java 11.

• Issue orchestrator #459 Check file existence in localstore
  A new endpoint HEAD /workflows/{workflow_id}/files/{attachment_id} has been added to the localstore to check if a file exists or not.
  The localstore now also checks if a file exists first to prevent some cases where it tried to delete non-existing ones.

---

Bug fixes

• Issue orchestrator #301 The observer should not expose 'out-of-scope' namespaces
  An execution environment could wrongly reject a workflow if it had one namespace where the token used to launch the workflow was not authorized.

• Issue micronaut-java-plugins #66 [Cypress interpreter] Parsing error on Windows environments
  The Cypress interpreter had issues to detect the correct test case when the test was executed on Windows. This is now fixed.