Skip to content

Squash Orchestrator 4.10.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.10.0 compared to 4.9.0.

Squash Orchestrator 4.10.0 was released on April 25, 2024.

New features

  • Issue micronaut-java-plugins #59 🔑 Build native image with option -march=compatibility
    Issue micronaut-java-plugins #84 Build native image with option -march=compatibility
    Compatibility issues in Squash Orchestrator version 4.8.0, which previously caused an error message stating "The current machine does not support all of the required CPU features by the image." have now been resolved.

  • Issue orchestrator #456 Generate a human-readable test status summary report HTML
    Issue orchestrator #466 Make insightcollector HTML configurable
    Issue orchestrator #479 Enhance Insight Collector generated HTML reports
    Issue orchestrator #489 Reverse the doughnuts tooltip title and content in the HTML report
    Issue orchestrator #510 HTML reports : Clouds should include the number of test in error
    Issue python-plugins #13 🔑 Ensure the logpublisher plugin can handle more than one workflow result
    Upon successful workflow completion, an HTML report summarizing the test execution outcomes is automatically generated. It is configurable through the Insight Collector Configuration file. Multiple reports can be set up. More information can be found here.

  • Issue orchestrator #476 Obtain a report from Insight Collector
    Insight Collector has a new user-facing endpoint: POST /workflows/<workflow_id>/insights. This endpoint is used by opentf-ctl generate report {workflow_id} using {definition_file} command to post insight definitions and demand report generations. More information can be found here.

  • Issue micronaut-java-plugins #60 🔑 Add execution time and error messages to testResult notifications
    Issue micronaut-java-plugins #71 Add execution time and error messages to testResult notifications
    The test result notifications in workflows have been updated to include duration and failure details. This information is later displayed in the HTML reports.

  • Issue micronaut-java-plugins #58 🔑 Add Squash TM version number information in autom publisher to manage legacy versions
    Support for managing legacy versions has been introduced, allowing for the addition of future features such as the "Skipped" execution status in Squash TM version 7.0 and later, while ensuring compatibility with older versions.

  • Issue micronaut-java-plugins #85 Robot framework parser should manage NOT RUN for step statuses
    Issue micronaut-java-plugins #80 Robot framework parser should manage SKIP new statuses
    The Robot Framework parser now supports "Skipped" and "Not run" step statuses. The new statuses will be available in Squash TM version 7.0 and later.

  • Issue micronaut-java-toolkit #52 Status report in TM on canceled workflow
    Issue micronaut-java-plugins #52 🔑 Status report in TM on canceled workflow
    Issue micronaut-java-plugins #55 🔑 Allow a user to kill a running workflow
    New elements have been added that will make it possible to stop test suite executions starting from Squash TM 7.0.

  • Issue micronaut-java-plugins #46 🔑 Improve generator error logs
    The generator logs, previously very technical, have been improved to be more comprehensible and user-friendly.

  • Issue micronaut-java-plugins #50 🔑 Replace PEaC with workflow
    The name "PEaC (Planned Execution as Code)" has been replaced with "workflow" in the generator error messages.

Bug fixes

  • Issue micronaut-java-plugins #64 🔑 GeneratorResult message is incomplete
    An issue causing inconsistencies in "GeneratorResult" messages between Orchestrator 4.7 (and later versions) and earlier versions has been resolved.

  • Issue orchestrator #490 [Hooks] Hooks from different provider merge their content
    If different provider hooks containing OTF actions are specified, the aggregator service no longer merges them.

  • Issue orchestrator #391 Cypress : parameters are not secured
    The parameters containing special characters used to break the Cypress provider script. They have now been secured.

  • Issue micronaut-java-plugins #38 Interpreter: Receiving an incorrect document should not generate a stacktrace
    Issue micronaut-java-plugins #63 🔑 Interpreter: Receiving an incorrect document should not generate a stacktrace
    Issue micronaut-java-toolkit #58 Interpreter: Receiving an incorrect document should not generate a stacktrace
    Issue micronaut-java-plugins #39 Allure collector: Receiving an incorrect document should not generate a stacktrace
    If the Interpreter or Allure collector receive an incorrect document, it handles the error without generating a stack trace with DocumentBuildingException/SAXParseException.

  • Issue orchestrator #493 Incorrect invalid YAML handling in receptionist
    Error handling has been implemented to prevent the generation of a stack trace when the receptionist receives a malformed YAML file.

  • Issue orchestrator #316 [Cucumber] Tags name can't contains all kind of special character
    Characters that the Cucumber provider does not support as Cucumber tags (space and the following characters: `, ', ", (, \, ,,&, ;, |, <, and %tag% (a string surrounded by percent signs) are now blocked by the Orchestrator.

  • Issue micronaut-java-plugins #74 Postman parser throws non-blocking error when test reference contains single quote in folder name
    Issue micronaut-java-plugins #83 Postman parser throws an illegalArgumentException error when attempting to parse the test report XML if the REST reference contains some special characters
    Postman Parser issues related to special characters in test references and request names have been resolved.