Sequential execution

Run flows in a specific order using executionOrder for dependent test scenarios.

By default, Maestro executes Flows in a non-deterministic order. This is intentional because testing Flows in isolation ensures they are robust and not dependent on side effects from previous tests.

However, there are scenarios, particularly in Goal-Driven Apps, where you need to validate a strict sequence of events (e.g., creating an account, then verifying a profile, then placing an order). In these cases, you can use the executionOrder configuration.

Configuring the sequence

To force an order, add the executionOrder block to your config.yaml. You can identify Flows using either their file name (without the .yaml extension) or the name property defined inside the Flow itself.

# config.yaml
executionOrder:
  continueOnFailure: false # Default is true
  flowsOrder:
    - signup_flow          # Step 1
    - verify_email_flow    # Step 2
    - complete_profile     # Step 3

When you configure executionOrder, Maestro will:

1. First, run the flows listed in flowsOrder sequentially, in the specified order.

2. After that sequence completes, run any discovered Flows that are not included in flowsOrder in a non-deterministic order.

Execution environment

Sequential execution is designed for local test runs only. On Maestro Cloud, tests are automatically parallelized across multiple virtual devices to provide the fastest possible feedback.

Handling failures

The continueOnFailure flag determines how the sequence behaves if a step fails:

• true (Default): If signup_flow fails, Maestro will still attempt to run verify_email_flow. This is useful for independent tests that happen to be ordered for convenience.

• false: If signup_flow fails, the entire remaining sequence is cancelled. This is essential for dependent tests where Step 2 cannot possibly succeed if Step 1 fails.

Best practices and isolation

Even when running in sequence, you should treat your Flows as isolated units. A good rule of thumb is:

Each Flow should be able to run on a completely reset device.

Do not rely on one Flow leaving the app in a specific state for the next one.

If you need to ensure a specific state (e.g., being logged in), use a Hook or a Nested Flow at the start of your test.

Requirement	Recommendation
Logic dependency	Use runFlow to nest the required setup inside the test.
Simple ordering	Use executionOrder in config.yaml.
Stop on error	Set continueOnFailure: false.

Example: Partial sequencing

If you have five Flows (A, B, C, D, E) but only care that A and B run first, you can use the following configuration for the executionOrder:

executionOrder:
  flowsOrder:
    - flowA
    - flowB

Maestro will run A, then B, and then run C, D, and E in any order.

Next steps

Now that you have defined how and when your tests run, learn how to view the results:

• Test reports and artifacts: Learn how to generate JUnit and HTML reports.

• AI test analysis: Use AI to find UI and logic issues in your completed runs.