Squash Orchestrator 3.7.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 3.7.0 compared to 3.6.0.

Squash Orchestrator 3.7.0 was released on September 23, 2022.

---

New features

• Issue orchestrator #171 SoapUI - Implement the [Windows] version of the provider.
  Windows execution environments are now supported for SoapUI.

• Issue orchestrator #173 ActionProvider Soap: Improved soapui/soapui action
  Inputs of the soapui/soapui@v1 action have been tidied up.

• Issue orchestrator #139 Add extra-options to the postman/postman@v1 action
  The postman/postman@v1 action now supports the extra-options input.

• Issue java-plugins #22 Support JUnit 5 annotations
  For JUnit 5, @RepeatedTest, @ParameterizedTest, @TestFactory, and @TestTemplate tests are now properly supported.
  (@Nested classes are still not fully functional.)

• Issue orchestrator #203 Handling of URL-rewriting proxies
  The orchestrator can now be configured to work properly when deployed behind a reverse proxy. This configuration is done via environment variables described in the documentation.

• Issue orchestrator #136 Inputs should be visible to hooks
  Hooks can now access the inputs of the provider, either by using the ìnputs context or via INPUT_<VARIABLE_NAME> environment variables.

• Issue python-toolkit #40 Add 'native' support for powershell/pwsh
  PowerShell can now be used in PEaC files.

---

Bug fixes

• Issue java-plugins #25 Cypress version 10.4.0 : The "blocked" status of the automated test execution is displayed even if the test is successful
  The orchestrator was failing to interpret the reports generated by Cypress latest versions in Windows environments.

• Issue orchestrator #218 Allow the JUnit Provider to print relevant error logs when the test reference is wrong
  When executing JUnit tests, the output of Maven was lost (e.g. when the test was not found). This has been fixed: Maven output is now properly reported in the orchestrator logs.

• Issue python-toolkit #38 Allow finer log level settings
  Issue otf-all-in-one-images #13 We need to modify the commands for launching java plugins to allow the display of the log level
  The DEBUG_LEVEL environment variable is now taken into account by the micro-services implemented in Java.

• Issue python-toolkit #46 DEBUG_LEVEL: default values are not displayed in the logs
  Orchestrator logs were not properly reporting default values of environment variables.

• Issue orchestrator #216 Action Provider get-files: check file existence before returning attachment when using a *. pattern
  The actions/get-files action now correctly manages the case when no files match the specified pattern, avoiding spurious error messages.

• Issue orchestrator #148 continue-on-error not working on actions
  continue-on-error is now working properly for actions.

• Issue python-toolkit #41 Names of the file parameters in a PEAC do not support hyphen '-'
  PEaC files now supports parameters whose name contains a hyphen.

• Issue python-toolkit #42 Display of CRLF characters in the execution logs of a Linux workflow
  CRLF was used in logs on Linux environments, this has been fixed: LF is now used.

• Issue python-toolkit #45 Improve handling of leading and trailing spaces in configuration files
  Issue orchestrator #223 pools file : a whitespace after the comma used to separate multiple namespace is interpreted
  Spaces in comma-separated configuration parameters are now ignored.

• Issue python-toolkit #44 Empty lines in token authorization files and trusted keys authorization files are not allowed
  It is now possible to have empty lines in files providing trusted keys.

• Issue python-toolkit #43 Verify the paths indicated in the trustedkeys_auth_file when launching the orchestrator
  An error is now properly reported if the file defined by the OPENTF_TRUSTEDKEYS_AUTH_FILE environment variable is not accessible.

• Issue python-toolkit #39 Unclear error if the subscription fails
  The failure of a service to subscribe to the EventBus is better handled and reported.

• Issue orchestrator #220 Occasional error when deploying Squash Orchestrator
  An error randomly occurring during the orchestrator launch has been fixed.