* Increase the timeout for asserting 'Be in your element' is visible * Disable the chrome onboarding flow. This simplifies the code a lot and helps avoid corner cases. * More delays with timeout! * Add more info to the summary, specially when the tests fail, so we can quickly check what failed. * Make sure Maestro tests can't run in parallel, but APK builds can
32 lines
833 B
YAML
32 lines
833 B
YAML
appId: ${MAESTRO_APP_ID}
|
|
---
|
|
- tapOn: "Sign in manually"
|
|
- runFlow: ../assertions/assertLoginDisplayed.yaml
|
|
- takeScreenshot: build/maestro/100-SignIn
|
|
- runFlow: changeServer.yaml
|
|
- runFlow: ../assertions/assertLoginDisplayed.yaml
|
|
- tapOn:
|
|
id: "login-continue"
|
|
## MAS page
|
|
- retry:
|
|
maxRetries: 3
|
|
commands:
|
|
- extendedWaitUntil:
|
|
visible:
|
|
id: "form-1"
|
|
timeout: 10000
|
|
- tapOn:
|
|
id: "form-1"
|
|
- inputText: ${MAESTRO_USERNAME}
|
|
- pressKey: Enter
|
|
- tapOn:
|
|
id: "form-3"
|
|
- inputText: ${MAESTRO_PASSWORD}
|
|
- pressKey: Enter
|
|
- tapOn: "Continue"
|
|
## Back to native world
|
|
- runFlow: ../assertions/assertSessionVerificationDisplayed.yaml
|
|
- runFlow: ./verifySession.yaml
|
|
- runFlow: ../assertions/assertAnalyticsDisplayed.yaml
|
|
- tapOn: "Not now"
|
|
- runFlow: ../assertions/assertHomeDisplayed.yaml
|