Implement ability to add onSuiteComplete/onSuiteStart in config.yaml

[PushkarPahare]

I'd like your feedback on adding onSuiteStart/onSuiteComplete functionality directly in config.yaml files. This would improve our test setup and teardown processes. Currently we handle the setup and teardown in external scripts. I have considered using flowOrder, but it has limitation continueOnFailure must be disabled to run the tear down.

Approaches I tried:

## Approach 1: Use flow order to execute setup and tear down: Config.yaml

flows:
  - '**'
executionOrder:
  continueOnFailure: false # default is true
  flowsOrder:
    - onSuiteStart.yaml
    - myTest.yaml
    - onSuiteComplete.yaml

# Approach 2: Script to sandwich the maestro call between setup and teardown.

setup.sh
maestro <arguments>
teardown.sh

Proposed change:

flows:
  - '**'
onSuiteStart:
  - <some script>
 onSuiteComplete:
  - <some script>  
executionOrder:
  continueOnFailure: false # would work with even if the value is true
  flowsOrder:
    - myTest.yaml

Key Benefits:

• Works regardless of continueOnFailure setting
• Simplifies test configuration
• Keeps setup/teardown logic within config.yaml

I would appreciate your thoughts on 1/ Technical feasibility and 2/ Implementation approach.

[Fishbowler]

I'd say that right now is problematic. The way Maestro works is inherently portable. As soon as you start adding external scripting languages or binaries into the mix, that all falls apart.

Where scripting like that is needed, I'd suggest using a wrapper script inside the domain, e.g.

set -e
./setup.sh
set +e
maestro test ./someFolder
./teardown.sh