Running a test folder vastly reduces the test output

[dialex]

Running a test:

$ maestro test test/file.e2e.yml

 ║  > Flow
 ║
 ║    ✅  Clear state of com.app
 ║    ❌  Launch app "com.app"
 ║    🔲 Assert that ".*Terms of Service.*" is visible
 ║    🔲 Tap on "Get started"
 ║    🔲 Input text something@gmail.com
 ║    🔲 Hide Keyboard
 ║    🔲 Tap on "Next"
 ║    🔲 Assert that "Verification code" is visible

• Where did it fail? Step 2.
• Why did it fail? You don't know 😢

Running a folder:

$ maestro test test

Waiting for flows to complete...

[Failed] file.e2e

1/1 Flow Failed

• Where did it fail? You don't know 😭
• Why did it fail? You don't know 😭

[cenci7]

I would love that change!

[lgawin]

I use JUnit report when running whole test suite:

maestro test --format junit test/

that brings more details ...

[Hema-ACS]

I used JUnit, but the error statement is not clear. Maybe we could get a chance to take a screenshot when it's failed

[simon-gilmurray]

Would be good to expand this reporting to reveal more about where and why it failed

[solidcell]

Even just having the output of running a folder be as verbose as running a single file would be great.

[bartekpacia]

related to #1674