Squash Orchestrator 4.12.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.12.0 compared to 4.11.0.
Squash Orchestrator 4.12.0 was released on August 13, 2024.
New features
-
Issue orchestrator #419 Optimize channel allocation for jobs
The orchestrator now allows parallel executions. This can be specified through thestrategy.max-parallel
option in a workflow. More information available here. -
Issue orchestrator #506 Allow to use the newly available execution time for testcases in html reports
New sections are now available for HTML reports to improve the exploitation of the execution time, such asBarCharts
,ProgressBar
,ScatterChart
. The default one has also been updated withBarCharts
andProgressBar
. More information available here. -
Issue orchestrator #213 Autom/Devops: simultaneous execution with available or/and unavailable environments
The orchestrator now allows jobs which do not have any dependencies to be selected as candidates for execution and no longer have a forced dependency with other jobs. -
Issue orchestrator #521 [XML-report] Make XML report testcase items names unique
To enhance compatibility with GitLab, testcase items now consist of unique names. -
Issue orchestrator #538 Add reasons to WorkflowCanceled events
Adetails.reason
was added toWorkflowCanceled
events to give more information about the origin of the cancellation. -
Issue orchestrator #532 Move qualitygate plugin to the orchestrator
The qualitygate is now a plugin of the orchestrator to make use of the new datasource endpoint. -
Issue orchestrator #531 Restrict exposition of status functions
Status functions (success()
,failure()
,cancelled()
, andalways()
) are now only allowed in conditionals and insight model selection. More information available here. -
Issue python-toolkit #136 Update workflow schema
The workflow schema has been updated due to new/future components. It is now possible to set the timeout directly in the workflow through thetimeout-minutes
keyword. More information here. -
Issue orchestrator #473 Logs from allinone does not give information about their origin
Serviceallinone
logs now expose their origin services to improve the readability. -
Issue orchestrator #393 Allow jobs to be skipped
Jobs now have access to the status skipped, for example, if a job has an unmet conditional. -
Issue micronaut-java-plugins #73 🔑 Prepare bringing testcase execution time to TM (squash-micronaut-java-plugins)
Issue micronaut-java-plugins #68 Prepare bringing testcase execution time to TM (otf-micronaut-java-toolkit)
Issue micronaut-java-plugins #97 Prepare bringing testcase execution time to TM (otf-micronaut-java-plugins)
The orchestrator now tracks the execution time of test cases. This information will be displayed starting with Squash 8.0.0.
Bug fixes
-
Issue squash-orchestrator #217 🔑 [SSL-Certificat]Can't run a orchestrator while using a CURL_CA_BUNDLE option
Due to the change of the default user from the previous version, the orchestrator couldn't add the certificates passed by the CURL_CA_BUNDLE variable to the Java store. This issue is now fixed. -
Issue orchestrator # 548 Incorrect phase for execution environments
In some case, execution environments were shown at an incorrect PENDING phase, now a proper phase is notified -
Issue python-toolkit #148 Incorrect handling of multi-lines variables on linux
Issue orchestrator #248 A variable containing a carriage return will be considered as multiple commands
Multi-line variables are now correctly handled. -
Issue micronaut-java-plugins #79 🔑 Inconsistent duration calculated in uft parser compared to result generated by UFT with 1ms difference
Issue micronaut-java-plugins #112 🔑 Inconsistent duration calculated in Robot parser compared to report HTML generated by Robot Framework with 1ms difference
Uniformization of the ways parsers calculate the duration of the execution time. -
Issue orchestrator # 482 Postman : folder name in the command line is not secured
Some special characters broke the command line, such as double quotes for Linux and percentage signs for Windows. This is now secured. -
Issue orchestrator # 377 Handle cleanup steps in case of ProviderCommand failure
A step with a missing required input will now be considered as a step failure rather than an error that cancels the workflow. -
Issue orchestrator #95 Run workflow with parameters returns error
The orchestrator now correctly handles expression syntax onruns-on
in a workflow.