Debug Output

View command failure reasons, automatic screenshots, and logs in Maestro. Configure debug output paths for test artifacts and reports.

Command Failure Reason

If a command fails, failure reason will be shown in red at the end.

Single Flow Run Failure

Multiple Flow Run Failures

Screenshot On Failure

By default, a screenshot will be generated upon failure under the Maestro directory i.e for Mac it's ~/.maestro/tests/<datetime>/

Maestro Logs

Each flow run will generate:

• A maestro.log file that contains Maestro related logs

• A commands-*.json file that contains command metadata

Located under the Maestro directory by default: ~/.maestro/tests/<datetime>/ .

You can also configure the default path for debug output by using the --debug-output <path> option. Example usage:

maestro test --debug-output /path/to/debug/logs

Configurable Test Output Directory

You can configure where Maestro stores test artifacts (screenshots, logs, and AI reports) using either:

1. Command line option: --test-output-dir

2. Workspace configuration: testOutputDir in config.yaml

maestro test workspace --test-output-dir=test_output_directory

Command line flag takes priority over workspace config, with fallback to default behavior.

For detailed configuration options, see the Test Output Directory documentation.

Device logs are not supported but it's something we plan to add

Such data will be automatically deleted after 14 days