You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the existing issues and didn't find mine.
Steps to reproduce
Hello,
Thank you for your help.
Put the config.yaml in the root project.
run "maestro test scenario" from windows (KO)
run "adb -a -P 5037 nodaemon server"
run "maestro test scenario" from the WLS (OK)
Config.yaml
flows:
- "./scenario/wifi/*"
Actual results
Only when i use the windows version, from powershell.
Error message :
> maestro test scenario
Top-level directories do not contain any Flows: C:\Users\xxx\Documents\Maestro\scenario
To configure Maestro to run Flows in subdirectories, check out the following resources:
* https://maestro.mobile.dev/cli/test-suites-and-reports#inclusion-patterns
* https://blog.mobile.dev/maestro-best-practices-structuring-your-test-suite-54ec390c5c82
Expected results
It's work fine when i use the WLS version.
"Waiting for flows to complete..." with the windows version .
About app
No specific app.
About environment
WLS Maestro version : 1.39.9
Windows Maestro versions : 1.39.9
Windows 11.
Ubuntu 24.04.1 LTS
Error in my ticket, it doesn't work on either Linux or Windows, the issue is probably with my config.yaml. I consistently get "Flow inclusion pattern(s) did not match any Flow files:"
Is there an existing issue for this?
Steps to reproduce
Hello,
Thank you for your help.
Config.yaml
Actual results
Only when i use the windows version, from powershell.
Error message :
Expected results
It's work fine when i use the WLS version.
"Waiting for flows to complete..." with the windows version .
About app
No specific app.
About environment
WLS Maestro version : 1.39.9
Windows Maestro versions : 1.39.9
Windows 11.
Ubuntu 24.04.1 LTS
Logs
No response
Maestro version
1.39.9
How did you install Maestro?
install script (https://get.maestro.mobile.dev)
Anything else?
No response
The text was updated successfully, but these errors were encountered: