Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Settings in config.yaml / executionOrder / flowsOrder are ignored - not working #2231

Open
1 task done
TsTeamDev opened this issue Jan 7, 2025 · 1 comment
Open
1 task done

Comments

@TsTeamDev
Copy link

Is there an existing issue for this?

  • I have searched the existing issues and didn't find mine.

Steps to reproduce

  1. in config.yaml set any of the following cases: (I tried only 1 case at a time in config)
    executionOrder:
    continueOnFailure: true
    flowsOrder:

#case 1
- install_message
- setting_tracking
- check_license

#case 2
- 1_ins-flow
- 2_ins-flow-2

#case 3
- startA
- startB

#case 4
- start_a
- start_b
- start_c

#case 5
- 1_ios-advanced-flow
- 2_ios-advanced-flow-2
- 3_ios-advanced-flow-3

  1. run the test suite for the folder containing the flows with the same name
    maestro test folderName/

Actual results

Using #case 1 as example
Flow order in config
- install_message
- setting_tracking
- check_license

  • the flow is executed is a different order regardless the setting in config file

Waiting for flows to complete...
[Passed] install_message (15s)
[Failed] check_license (19s) (Assertion is false: "Lizenzvertrag" is visible)
[Passed] setting_tracking (6s)

  • the same issue happens for all the cases mentioned above
  • which means the sequence order, name or numebering is not taken into account
  • set a,b,c
  • execution does c,a,b

Expected results

If we set Flow order in config

  • install_message
  • setting_tracking
  • check_license

or

  • flow1
  • flow2
  • Flow3

or

  • flow_a
  • flow_B
  • etc..

the execution sequence order should be as configured in config.

Or please create a name logic that can be applied always in test suites for the execution folder or folders.

About app

  • Happens always on any flow with any app.
  • react native

About environment

  • java --version
    java 17.0.9 2023-10-17 LTS
    Java(TM) SE Runtime Environment (build 17.0.9+11-LTS-201)
    Java HotSpot(TM) 64-Bit Server VM (build 17.0.9+11-LTS-201, mixed mode, sharing)
  • Maestro version: 1.39.7
    OS: Mac OS X
    OS version: 14.1.1
    Architecture: x86_64

Logs

Logs
<!-- Replace this line with your logs. *DO NOT* remove the backticks! -->

Maestro version

1.39.7

How did you install Maestro?

install script (https://get.maestro.mobile.dev)

Anything else?

No response

Copy link

linear bot commented Jan 7, 2025

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant