Aller au contenu

Squash Orchestrator 4.0.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.0.0 compared to 3.8.0.

Squash Orchestrator 4.0.0 was released on March 2nd, 2023.

New features

  • Issue orchestrator #260 Support of Cypress projects which are not at the root of the Git repository
    Issue java-plugins #43 Update Cypress parser for the new Cypress test reference syntax
    The Orchestrator now supports Cypress tests which are anywhere in a Git repository. This required to modify the syntax of the test reference, but the old syntax is still supported.

  • Issue orchestrator #207 Add extra_options to robotframework/robot action
    The robotframework/robot action now supports the extra-options input, allowing the addition of any option on the Robot Framework command line.

  • Issue orchestrator #245 Add extra_options to junit/mvntest action [Was: The native maven command should allow for a custom settings.xml specification]
    The same for the junit/mvntest action.

  • Issue orchestrator #208 Add extra-options to cypress/cypress action
    The same for the cypress/cypress action.

  • Issue python-toolkit #55 Handle verbatim variables and secrets
    The Orchestrator now supports the definition of variables which are not interpreted by the shell (i.e. no expansion nor substitution is performed) by using the verbatim: true option, see the OpenTestFactory documentation.

  • Issue python-toolkit #58 Normalize inputs names
    The characters - and _ can now be freely interchanged in the input names (e.g. extra-options and extra_options are the same). - should be preferred.

  • Issue orchestrator #298 The eventbus should retry publication in case of communication failure
    In the case of communication failure, the EventBus will retry to publish the event (the max number of retries is defined by max_publication_attempts in the EventBus configuration file).

  • Issue orchestrator #283 Agent deregistration not explicit in logs
    Issue orchestrator #296 Improve agentchannel logs
    Additional information is logged when using agents:

    • deregistration of an agent;
    • sent and awaited files by an agent;
    • in debug mode, job assignation to/release from an agent.

  • Issue python-toolkit #50 Suppress/hide the Flask error message when starting the orchestrator
    The Orchestrator now uses a WSGI server, Flask is no longer directly accessed. The disturbing This is a development server. Do not use it in a production deployment. message is not present anymore in the logs.

  • Issue orchestrator #292 The eventbus logs are way too verbose in DEBUG mode
    The EventBug logs are easier to read when the Squash Orchestrator in debug mode.

Bug fixes

  • Issue python-plugins #11 🔑 OpenTF Ready Mismatch for tm.executionlogpublisher
    opentf-ready was broken in 3.8.0. It has been repaired.

  • Issue java-plugins #40 Failure to parse a report if the Robot Framework test reference contains a dot
    The parsing of Robot Framework reports was failing if the tests were declared, in Squash TM, as being in directory .. This is now supported.

  • Issue java-plugins #41 Allure Robot Framework : UnrecognizedPropertyException if the robot test contains documentation on the test case
    The Squash Orchestrator was failing to parse Robot Framework reports for tests having a [Documentation] setting. It should now support any setting.

  • Issue orchestrator #290 Test ref RobotFramework: Special characters are interpreted as regex in robot Test case name
    Issue java-plugins #36 Parser crash when the Robot Framework test reference contains a double quote
    Issue orchestrator #266 Double quotes are lost in name of Robot Framework tests
    Robot Framework tests whose name contains an asterisk (*), question mark (?), square bracket ([ and ]), or double quote (") are now supported. There are still problems with test names containing a backslash character (\), they will be fixed in the next release.

  • Issue java-plugins #35 Parser crash when the Cucumber test reference contains a double quote
    Cucumber tests whose name contains a double quote (") are now supported.

  • Issue orchestrator #255 Actions inputs are not converted as environment variable if they contain tabs
    Function inputs containing special characters were not transmitted as environment variables (see the mechanism described in the OpenTestFactory documentation), this limitation has now been fully removed, including for tab characters. This is the continuation and end of Issue orchestrator #243 implemented on 3.8.0.

  • Issue orchestrator #276 Incorrect filter in arranger.py in setting environment variables with quote characters.
    It is now possible to define action inputs containing a double quote (") character.

  • Issue java-plugins #16 🔑 Modify error message when the "premium" environment variable is missing/is present
    The error message logged when the Squash Orchestrator was launched in community mode while connected to a Test Plan Retriever plugin in premium version was misleading. It has been changed.