Enhance "Run All Tests" to Support Recursive Execution in Nested Directories and Exclude Configuration Files

[ryuuhei0729]

Problem

Currently, the "Run All Tests" button in Maestro Studio has two limitations:

1. Includes non-test YAML files: The button executes all .yaml files in the current directory, including configuration files (e.g., workspace configuration YAMLs) that are not actual test flows. This causes errors or unintended behavior when trying to run all tests.

2. Does not support nested directories: The button only executes test files in the current directory and does not recursively discover tests in subdirectories. Users typically organize their test flows in nested directory structures like:

   maestro/
   ├── auth/
   │   ├── login.yaml
   │   └── logout.yaml
   ├── register/
   │   └── signup.yaml
   └── config.yaml  (configuration file, not a test)
   

Expected Behavior

The "Run All Tests" button should:

• Recursively discover and execute all test files in the current directory and all its subdirectories (similar to maestro test maestro/**/*.yaml in CLI)
• Exclude configuration files and only execute actual test flow files

Current Workaround

Users can work around this limitation by using the CLI:

maestro test maestro/**/*.yaml

However, this defeats the purpose of using Maestro Studio's no-code UI approach.

Proposed Solution

Modify the "Run All Tests" functionality to:

1. Recursively scan the current directory and all subdirectories for test files
2. Filter out configuration files (e.g., config.yaml, workspace.yaml, or files that don't contain Maestro flow commands)
3. Execute all discovered test files in a batch

This would align Maestro Studio's functionality with the CLI capabilities while maintaining the convenience of the GUI.

[Fishbowler]

I think this would do better to instead honour the config.yaml and use that to work out which tests to run.

Consider this directory structure:

/
├── partials/
│   └── launch-app.yaml
│   └── logIn.yaml
├── tests/
│   ├── featureA
│   │   ├── test1.yaml
│   │   └── test2.yaml
│   └── featureB
│       ├── test1.yaml
│       └── test2.yaml
├── scripts
│   └── setSomeVariables.js
└── config.yaml

You don't want partials being executed. You'd want the config.yaml to contain

flows:
  - tests/**

and for Studio to honour that when you hit Run All Tests.

Right?