New Field: suiteName

[lucasdiblasi-avenue]

Use case

Suggestion for Improvement to the Maestro Framework

New Field: suiteName

Motivation: Adding the "suiteName" field will allow the separation of flows by suite, making report organization easier.

Example:

appId: my.app
suiteName: Github Actions
name: Create a new Issue.

With this structure, flows can be organized more clearly and efficiently, improving the management and visualization of reports.

Proposal

appId: my.app
suiteName: Github Actions
name: Create a new Issue.

Anything else?

No response

[linear]

MA-3019 New Field: suiteName

[Fishbowler]

Thinking about implementation, the YamlConfig class is already special - any key that isn't specified ends up in config.ext. The jsEngine is configured this way - with no direct Yaml definition.

This makes the implementation easier, since we don't need do plumbing all the way back to the parsing.

Also, worth considering that suiteName is already in use at a run level, e.g. maestro test --test-suite-name "App v1.3 Release" ./myTests so we'd need a different name for a logical collection of 'some related tests'