---
title: Knowledge check | Maestro Mobile Testing | TestingBot
description: Ten questions on the decisions you will actually face when writing and
  running Maestro flows. Pick an answer for each, then check them all at once. 1.
  A…
source_url:
  html: https://testingbot.com/resources/courses/maestro/knowledge-check
  md: https://testingbot.com/resources/courses/maestro/knowledge-check.md
---

Course

[Maestro Mobile Testing](https://testingbot.com/resources/courses/maestro)

Chapter 10 of 10

1. [1 Maestro Tutorial: Mobile UI Tests in YAML](https://testingbot.com/resources/courses/maestro)
2. [2 Install Maestro and Run Your First Flow](https://testingbot.com/resources/courses/maestro/install-and-first-flow)
3. [3 Maestro Selectors and Core Commands](https://testingbot.com/resources/courses/maestro/selectors-and-commands)
4. [4 Subflows, Conditions, Loops and JavaScript](https://testingbot.com/resources/courses/maestro/flow-control-and-javascript)
5. [5 iOS vs Android: Permissions, State, Links](https://testingbot.com/resources/courses/maestro/ios-and-android-specifics)
6. [6 Debugging Flaky Maestro Flows](https://testingbot.com/resources/courses/maestro/debugging-and-flakiness)
7. [7 Organising a Maestro Suite](https://testingbot.com/resources/courses/maestro/organising-a-suite)
8. [8 Run Maestro Flows on TestingBot](https://testingbot.com/resources/courses/maestro/run-on-testingbot)
9. [9 Running Maestro in CI Pipelines](https://testingbot.com/resources/courses/maestro/ci-pipelines)
10. [10 Knowledge check](https://testingbot.com/resources/courses/maestro/knowledge-check)

[Exit course](https://testingbot.com/resources/courses)

 Chapter 10 of 10 Beginner 5 min read Updated Nov 2026 

# Knowledge check

Ten questions on the decisions you will actually face when writing and running Maestro flows. Pick an answer for each, then check them all at once.

1. A field already contains `0`. Your flow taps the field, runs `eraseText`, types `10`, and the field shows `100`. What is the most likely cause?

 `eraseText` only works on Android The tap put the cursor before the existing `0`, and backspace had nothing to its left to delete `inputText` appends a zero to numeric fields

`eraseText` sends backspace presses, which delete to the left of the cursor. Tapping the right-hand side of the field, for example with `point: "90%,50%"`, puts the cursor after the existing text.

2. The Total field shows `150`. Does `assertVisible: "15"` pass?

 Yes, because `15` is contained in `150` Yes, but only on iOS No, text selectors are regular expressions that must match the whole text

Text and id selectors match the full string as a regex. Use `.*15.*` if you really want a partial match, which here would have hidden the bug.

3. Your app's labels are translated into six languages. Which selector is the most robust for the "Submit" button?

 An `id` (resource id on Android, accessibilityIdentifier on iOS) `text: "Submit"` `point: "50%,90%"`

Ids are invisible to users and do not change with the language. Text changes per locale, and screen coordinates change per device.

4. You run `maestro test .maestro/`, and your flows live in `.maestro/auth/` and `.maestro/checkout/` with no `config.yaml`. What runs?

 Every flow in every subfolder Only flow files at the top level of `.maestro/`, so none of them Only flows that have tags

Without a `flows` pattern in `config.yaml`, Maestro only runs top-level files. That same default is what keeps `subflows/` from running on its own.

5. You run with `--include-tags=smoke --exclude-tags=flaky`. Which flows run?

 Untagged flows plus flows tagged `smoke` Flows tagged `smoke`, including those also tagged `flaky` Flows tagged `smoke` that are not tagged `flaky`; untagged flows are skipped

Include is applied first, then exclude removes matches. With an include filter, untagged flows never run, which surprises people the first time.

6. A flow's header has `env: { A: "7" }`. You want `maestro test -e A=20 flow.yaml` to type 20, and 7 when no value is passed. What should the header say?

 `A: ${A || "7"}` Nothing needs to change; `-e` always overrides the header `A: "${A}"`

In our test run, a fixed constant in the header won over `-e`. A JavaScript default keeps a passed-in value and falls back to 7 otherwise.

7. A payment confirmation screen sometimes takes 20 seconds to appear and the flow fails with "not visible". Which fix is the right one?

 Wrap the whole flow in `retry` with `maxRetries: 3` `extendedWaitUntil` with `visible: "Payment confirmed"` and a realistic `timeout` Add `retryTapIfNoChange: true` to the pay button tap

Assertions only wait a few seconds. `extendedWaitUntil` waits up to an explicit timeout and moves on as soon as the element appears; a whole-flow retry repeats the payment and hides real problems.

8. On iOS, `clearState` resets your app, but the app still starts logged in with a token it stores in the Keychain. What do you add?

 `stopApp: false` `permissions: { all: deny }` `clearKeychain: true` on `launchApp`

The Keychain is cleared by its own option. `stopApp: false` resumes a backgrounded app, and permissions are unrelated to stored credentials.

9. On TestingBot, you run 12 flows with no extra options and your plan allows 2 concurrent sessions. What happens?

 Each flow gets its own session; 2 run at a time and the rest queue All 12 flows run in one session, one after another The run is rejected because it exceeds your concurrency

By default every flow runs in a separate session, and sessions beyond your concurrency are queued. `--shard-split 1` would put all flows in one session instead.

10. In CI, the TestingBot CLI exits with code 2. What does that tell you?

 The upload failed or the credentials are missing The run completed and one or more flows failed The run is still in progress

0 means all flows passed, 2 means flows failed, and 1 is a CLI or infrastructure error. Keeping them apart lets a pipeline retry infrastructure problems without hiding test failures.

Check answers

From here, the [TestingBot Maestro documentation](https://testingbot.com/support/app-automate/maestro) covers the REST API, tunnels and every run option in more depth. If you also maintain WebDriver-based mobile tests, the [Appium with WebdriverIO course](https://testingbot.com/resources/courses/appium-webdriverio) is the natural next step.

[Previous · Chapter 9 Running Maestro in CI Pipelines](https://testingbot.com/resources/courses/maestro/ci-pipelines)
## You finished Maestro Mobile Testing

Put what you learned into practice. Run your tests on 6100+ real browsers and physical iOS and Android devices.

[Start free trial](https://testingbot.com/users/sign_up) [See pricing](https://testingbot.com/pricing) [Browse other courses](https://testingbot.com/resources/courses)

## TestingBot Maestro Certification

Turn this course into a free, resume-worthy credential: pass the exam, run the course suite on TestingBot, and get a verifiable certificate for your LinkedIn profile.

[How it works](https://testingbot.com/resources/courses/maestro/certification)
