Aller au contenu

Squash Orchestrator 4.9.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.9.0 compared to 4.8.0.

Squash Orchestrator 4.9.0 was released on February 14, 2024.

Note

The Squash Ultimate exclusive micro-services are now integrated in this image.

New features

  • Issue squash-orchestrator #129 🔑 Move the Premium micro-services in the standard images and protect them with the license
    Issue squash-orchestrator #136 🔑 Remove SQUASH_LICENCE_TYPE=premium option
    The Squash Ultimate micro-services are now in the squash-orchestrator image. They are now automatically enabled if a license is mounted in the container (either through the LICENSE_PATH environment variable or at the default location /app/license/squash-tm.lic). Previous Premium features are also activated by the same mechanism. More information can be found here.

  • Issue orchestrator #457 Make the generated execution log configurable
    Issue orchestrator #467 Enhance Insight Collector execution log configurability
    A new insightcollector service is available to allow users to configure the execution log automatically generated after every workflow execution. This is done through a configuration file set by the INSIGHTCOLLECTOR_CONFIGURATION environment variable. More information can be found here.

  • Issue orchestrator #465 Allow pinging and dryrunning the receptionist service
    The receptionist service can now be pinged or requested in dry-run mode on its endpoint. This can be used to test new deployments or check if a workflow is correct or not. More information can be found here.

  • Issue micronaut-java-plugins #64 Junit5 @nested: Get the right status of the execution results
    JUnit @Nested tests are now supported. A new syntax has been introduced to deal with them. More information here.

  • Issue python-toolkit #119 Allow for configurable service aggregators
    A new allinone service is available to manage open-source providers. This is used primarily to reduce the memory consumption.

  • Issue orchestrator #464 Robot Framework: misleading warning message
    After a Robot Framework execution, if the Allure library did not generate *-attachment.html files then it may have resulted in an incorrect log that could confuse users. The log has been removed. The get-files action has also been improved with a new skip-if-not-found option to remove the error message if no files were found.

Bug fixes

  • Issue micronaut-java-toolkit #44 [jackson.dto]The status can't handle all windows error code level (only integer)
    Some Windows error codes could exceed the maximum value accepted by a 32-bits integer, causing an error in the Java services.

  • Issue micronaut-java-plugins #77 Cypress interpreter : results not found if the test does not have a test suite
    A Cypress test without its own test suite was not interpreted correctly by the parser.

  • Issue micronaut-java-plugins #40 🔑 [Generator]Generator break if the TMUrl parameter end with a "/"
    A call to the generator with the squashTMUrl ending with a trailing slash could generate an error.

  • Issue orchestrator #451 Workflows are not cleaned up
    Some logs (in TRACE) not related to a workflow were sent like they were, causing some workflows to appear again (with name and status set to <none>) after they were cleaned up in the workflow list.

  • Issue micronaut-java-plugins #44 🔑 Remove the path property in generated workflows
    params actions in workflows generated by Squash TM contained an obsolete input. It has now been removed.