Aller au contenu

Squash Orchestrator 3.4.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.4.0 compared to 3.3.0.

Squash Orchestrator 3.4.0 was released on March 30, 2022.

New features

  • Issue qualitygate #1 Implement basic quality gate
    Issue orchestrator #57 Quality Gate
    Squash Orchestrator can now be used as a quality gate in a CI/CD pipeline.
    The current implementation supports two configurations:

    • strict: the quality gate will be successful if all test results are OK and the workflow completed successfully.
    • passing: the quality gate will be successful if the workflow completed successfully, whatever the test results are.

    See the OpenTestFactory specification for the details on how to use it.

  • Issue orchestrator #81 lifting logs to workflows whenever possible
    We started to improve log management: some micro-services (the ones used to drive tests) are reporting more information. This information is available in opentf-ctl get workflow and in the Jenkins plugin.
    Later on, we will make the logs also available in Squash TM. We will also complete all micro-services so they provide the information necessary for trouble shooting.

  • Issue orchestrator #99 allow observer retention period configuration
    The event retention period of the Observer can now be configured with retention_period_minutes (see the documentation).

Bug fixes

  • Issue java-plugins #8 Filter localprocess stdout close failure warning in the allure collector
    The logs of Squash Orchestrator used to contain some java.io.IOException: Stream closed stack traces while, in fact, there was no failure. These stack traces are not present anymore.

  • Issue orchestrator #102 Incorrect JSON report for Cucumber
    When running a Cucumber test, a report.json file was generated, but its content was not some JSON data, but Cucumber terminal output. This file is no more generated.

  • Issue orchestrator #107 Renaming Robot Framework report files breaks links between files
    Issue orchestrator #109 Include Robot Framework attachments in the tar file
    When running a Robot Framework test, the generated report.html and log.html files were renamed and recorded in Squash TM. But this renaming resulted in breaking the hypertext links between the two files.
    Now, these files are not renamed anymore. Instead, a tar file containing them and, additionally, the screenshots generated during the test, is recorded in Squash TM.

  • Issue orchestrator #104 channel_id missing in some ExecutionError events
    When investigating problems, the channel_id is now available in the logs.

  • Issue orchestrator #105 Error trace after cleaning events
    Agents deregistered before being assigned a job do not generate error logs anymore.