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
Describe the bug
Tests are always running in parallel despite setting the flowsOrder, which is a bit confusing because this doc clearly outlines that other tests should run right after Flow A, without adding them explicitly in flowsOrder.
What happens is that, the rest of the flows not added explicitly, and in order in flowsOrder are opening the app in a logged out state. Flow A represents a login existing user flow in our project.
To Reproduce
Set the executionOrder to:
executionOrder:
continueOnFailure: false
flowsOrder:
- Flow A
Run maestro cloud
Expected behavior
Flow A should run first before everything else
Environment information (please complete the following information):
Maestro version: 1.35.0
Platform: Maestro Cloud
Framework: Flutter
Device model and OS version: Android
Workspace (if applicable)
You can browse our files here, needs authentication.
The text was updated successfully, but these errors were encountered:
Describe the bug
Tests are always running in parallel despite setting the
flowsOrder
, which is a bit confusing because this doc clearly outlines that other tests should run right after Flow A, without adding them explicitly inflowsOrder
.What happens is that, the rest of the flows not added explicitly, and in order in
flowsOrder
are opening the app in a logged out state. Flow A represents a login existing user flow in our project.To Reproduce
executionOrder
to:maestro cloud
Expected behavior
Environment information (please complete the following information):
Workspace (if applicable)
You can browse our files here, needs authentication.
The text was updated successfully, but these errors were encountered: