Skip to content

Squash Orchestrator 4.3.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.3.0 compared to 4.2.0.

Squash Orchestrator 4.3.0 was released on May 25, 2023.

New features

  • Most Java micro-services have been rewritten to consume less memory: the orchestrator’s Docker container now requires 2GB, instead of 5GB previously.

  • Issue orchestrator #347 Retrieval of Cypress screenshots
    Screenshots generated during a Cypress test are now collected and transferred as a tar file in Squash TM (in addition to the Surefire report that was previously the only recorded test artefact).
    For this purpose, Cypress is instructed (with the --config screenshotsFolder=<directory> command line option) to store the screenshots in a directory. Hooks of the cypress/execute@v1 action can get the name of that directory via the OPENTF_CYPRESS_SCREENSHOT_FOLDER environment variable.

  • Issue orchestrator #360 Change sshchannel connexion logs level
    The SSH channel plugin logs are less verbose: information messages are no more reported except if the log level (defined by the DEBUG_LEVEL or SSHCHANNEL_DEBUG_LEVEL environment variables) is set to DEBUG.

  • Issue orchestrator #372 Normalize incoming steps so that they all have IDs
    If a workflow contains some steps with no IDs, the orchestrator will assign some generated ones. This will help for the log analysis.

  • Issue orchestrator #374 Publish notifications for step status (outcome and conclusion)
    In order to further help the log analysis, a notification is generated for each step, it contains the ID, outcome, and conclusion of the step.

Bug fixes

  • Issue orchestrator #373 Cucumber 4 : chaining multiple tests will break while trying to clean up the html report
    A regression was introduced in 2023-04 delivery: running several Cucumber 4 tests was resulting in the workflow failing on the second test.

  • Issue orchestrator #353 Improper management of technical KOs
    Technical failures (e.g. trying to run a non-existing test) are not always properly handled. This has been improved for Robot Framework, Cucumber, and JUnit: the test will be reported as Blockedin Squash TM and the other tests will be executed.
    There are still some situations, such as for some of the other test technologies or a missing POM file, where the workflow is stopped and, hence, the last tests are not executed. They will be fixed in future releases.

  • Issue java-plugins #15 Improve error message when Squash TM's test plan contains no tests
    The error message in case an iteration or a test suite is executed, while it contains no automated test, was misleading: it used to indicate that the iteration / test suite does not exist.
    The message has been corrected.

  • Issue python-plugins #9 Log messages are not always clear if the log publisher fails to publish.
    If the Squash Publisher plugin fails to publish the execution log to Squash TM, there is now an ERROR in the logs (it used to be a WARNING before), and the target endpoint is indicated.

  • Issue micronaut-java-plugins #27 The Java services subscribe to broad events and complain when receiving them
    Some Java micro-services badly configured their message subscriptions, this has no functional effect, but some spurious error messages were logged.

  • Issue orchestrator #354 Outcome and conclusion missing in steps context for functions
    Using steps.<step id>.outcome to evaluate the result of a step completed successfully was generating an error.

  • Issue orchestrator #355 Updated tags are not taken into account for busy ssh execution environments
    Modifications of a pool definition were ignored if they were performed while the SHH channel was busy.