Squash Orchestrator 4.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 4.4.0 compared to 4.3.1.
Squash Orchestrator 4.4.0 was released on July 11, 2023.
New features
-
Issue qualitygate #11 Evaluation of the quality gate result
The orchestrator now supports defining a quality gate by providing a list of criteria, each criterion being defined by a minimal success threshold that must be reached for a given type of test (e.g. Postman tests must be 100% successful and at least 90% of the Cypress tests must be successful, in order to the quality gate to be successful as a whole). Read the OpenTestFactory documentation for the details of configuring and evaluating a quality gate. -
Issue orchestrator #11 Hooks for jobs
Hooks can now be defined to be applied just before or just after the setup / the teardown of a job (i.e. just before or just after the creation / the deletion of the execution workspace). These hooks will allow, for example, to:- use a given workspace, instead of creating a new one as it was always the case in previous Squash Orchestrator releases, by specifying this workspace in the
before
hook of a job setup; - preserve the workspace, instead of deleting it, by specifying to keep it in the
before
hook of a job teardown.
- use a given workspace, instead of creating a new one as it was always the case in previous Squash Orchestrator releases, by specifying this workspace in the
-
Issue micronaut-java-plugins #30 Configurable Surefire parser
Issue micronaut-java-plugins #40 Setup validation for parser configuration file
Issue otf-all-in-one-images #33 Easy user-defined configuration of the generic Surefire parser
Issue micronaut-java-plugins #49 Refactor external configuration file mechanism to prevent redefining other properties than parsers
In order to further reduce memory consumption and to facilitate the support of new test technologies, the parsers used to interpret Surefire reports for each technology (JUnit, Cucumber, Cypress…) have been replaced by a single configurable parser. This one is configured for the current test technologies supported by Squash Orchestrator, but that configuration can easily be extended for another new test technology generating Surefire reports, see the details here. -
Issue python-toolkit #86 Adding a
contains
function to be used in expressions
Some new functions are available in expressions:contains
,startsWith
,endsWith
,toJSON
, andfromJSON
. -
Issue python-toolkit #91 Unknown entries in contexts should resolve as ''
If a property is undefined in a context, it will now be evaluated as an empty string instead of generating an error. -
Issue micronaut-java-plugins #28 The test case origin is lost on test result notifications
The result notification message now contains the list of all test attachments and, for each test, the ID of the attachment used to determine the test status. -
Issue orchestrator #395 Reduce severity for channel handler 'no channel available' logs
The log indicating that there is no SSH channel or no agent channel for the technology of the test being launched is now anINFO
instead of aWARNING
.
Bug fixes
-
Issue otf-all-in-one-images #31 Micronaut services are not set to DEBUG while using the usual settings
The microservices ported to Micronaut were not properly taking into account the configured debug level. -
Issue micronaut-java-plugins #33 Result aggregator fails to cancel its workers if workflows are killed instantly
When a workflow was killed, Squash Orchestrator was sometimes remainingBUSY
because one of the microservices (the result aggregator) was improperly handling a workflow cancellation done quickly after its start. -
Issue python-toolkit #90 On windows, backslashes should not be escaped for verbatim environment variables
Verbatim variables containing a backslash (\
) were wrongly escaped on Windows.