actions-marketplace-validations/maestro-test-action
Simple step to run Maestro tests with GitHub Actions
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stalelast commit Dec 18, 2022
- License
- MIT
- Runtime
- Deprecated runtime
Pinned Snippet
uses: actions-marketplace-validations/dnihze_maestro-test-action@bda8a93211c86d0a05b7a4597c5ad134566fbde4 # no releases — HEAD as of 2026-07-12tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| env | Meastro environment variables, support | no | "" |
| flow | Meastro flow or directory | no | — |
| report | JUnit report destination | no | maestro/reports/test.xml |
| screenshots-dir | Relative or absolute path to where screenshots should be stored | no | maestro/screenshots |
| version | Maestro CLI version | no | latest |
Outputs
| name | description |
|---|---|
| report | Absolute path to JUnit test report |
| screenshots-dir | Absolute path to maestro screenshots placements |