Aller au contenu

Squash Orchestrator 3.6.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.6.0 compared to 3.5.0.

Squash Orchestrator 3.6.0 was released on July 25, 2022.

New features

  • Issue java-toolkit #43 The error message on invalid public keys is not clear.
    Issue java-plugins #1 🔑 Logs are not explicit: they show thread IDs, not service names, and services emits logs in different formats
    Issue java-plugins #3 Logs are not explicit: they show thread IDs, not service names, and services emits logs in different formats
    Issue java-plugins #3 🔑 Logs do not provide comparable information
    [SQUASH-4636 🔑] Specifically detect and report community/premium mismatch between the Squash TM test plan retriever plugin and the Squash TM Generator
    Issue java-toolkit #42 We need to modify the toolkit to harmonize logs format in java services
    Issue java-plugins #4 🔑 Improving publisher and generator logs
    Many log messages have been improved or added in order to simplify the analysis of problems (in particular in case of an improper configuration).

  • Issue orchestrator #177 Reduce observer memory usage
    The effort to reduce memory consumption continues: on this release, the Observer uses disk to reduce the amount of used RAM.

  • Issue orchestrator #119 Enable the use of the java-param-lib for Cucumber test
    The opentestfactory-java-param-librarycan now be used for Cucumber tests as was already possible for JUnit tests, see the Cucumber documentation.

  • Issue python-toolkit #36 Simplify provider hooks definition
    For a given provider, a {provider_name}_PROVIDER_HOOKS environment variable can be used to define a file containing the hook definitions.

  • Issue python-toolkit #31 Detect some invalid public keys
    A message now clearly indicates when a key is improperly formatted.

  • Issue orchestrator #121 Use advanced wildcard pattern format in create-archive action
    The actions/create-archive@v1 action now supports **/*.png or **/screenshot.png patterns.

Bug fixes

  • Issue otf-all-in-one-images #8 Unexpected service registration address
    In some cases, the endpoint were wrongly registering themselves with 0.0.0.0 as IP address.

  • Issue python-toolkit #32 An incorrect policy file can lead to an internal server error
    Policy files are now validated when the container is started. If one is incorrect, an error message is generated and the container stops.

  • Issue python-toolkit #21 Agents produce spurious error messages if the current working directory contains a space
    The agent was still improperly handling paths containing a space on Windows. This has been fixed in the orchestrator.

  • Issue orchestrator #175 Performance issue with agents
    The agent performance optimisation done in Orchestrator 3.2.0 was not effective in some cases.

  • Issue python-toolkit #34 Having the environment variable OPENTF_AUTHORIZATION_MODE=ABAC should be mandatory when launching the orchestrator with OPENTF_TOKEN_AUTH_FILE
    It was possible to launch the Orchestrator without any error with only OPENTF_TOKEN_AUTH_FILE environment variable.

  • Issue orchestrator #182 put-file broken on agents
    The actions/put-file@v1 action was not working for execution environments connected via the agent.

  • Issue orchestrator #12 put-file does not return an error if the target path is invalid
    An error is now generated when using the actions/put-file@v1 action on a non-existing file.

  • Issue orchestrator #149 RobotFramework: compromised transmitted parameters from TM to robot test when special chars like $
    Robot Framework tests can now use Squash TM datasets containing any character.

  • [SQUASH-5103 🔑] Postman : the collection name is not mentionned in the allure report
    Allure reports were improperly generated for Postman tests in the case where several tests have the same name. The hierarchy of the tests, as reported in the Allure report, has been tidied up to properly handle this situation.

  • Issue java-plugins #15 SoapUI - Test suite execution in blocked status
    The orchestrator was failing to parse the result of a SoapUI suite execution.