---
title: 'Knowledge Check | Mobile App Testing: From First Test to CI'
description: 'Ten questions on the decisions this course covered: where to run a test,
  which framework fits, how builds reach devices, and how to read a failure. Answer…'
source_url:
  html: https://testingbot.com/resources/courses/mobile-app-testing/knowledge-check
  md: https://testingbot.com/resources/courses/mobile-app-testing/knowledge-check.md
---

Course

[Mobile App Testing: From First Test to CI](https://testingbot.com/resources/courses/mobile-app-testing)

Chapter 10 of 10

1. [1 Mobile App Testing: What Makes It Different](https://testingbot.com/resources/courses/mobile-app-testing)
2. [2 Emulators, Simulators and Real Devices](https://testingbot.com/resources/courses/mobile-app-testing/emulators-simulators-and-real-devices)
3. [3 Choosing a Framework: Appium, Espresso, XCUITest, Maestro](https://testingbot.com/resources/courses/mobile-app-testing/choosing-a-framework)
4. [4 Uploading and Managing App Builds](https://testingbot.com/resources/courses/mobile-app-testing/app-builds-and-uploads)
5. [5 Your First Appium Test on a Real Device](https://testingbot.com/resources/courses/mobile-app-testing/first-appium-test)
6. [6 Your First Maestro Flow on TestingBot](https://testingbot.com/resources/courses/mobile-app-testing/first-maestro-flow)
7. [7 Running Espresso and XCUITest Suites in the Cloud](https://testingbot.com/resources/courses/mobile-app-testing/espresso-and-xcuitest)
8. [8 Device Matrix, Parallel Runs and CI](https://testingbot.com/resources/courses/mobile-app-testing/device-matrix-parallel-ci)
9. [9 Debugging Failed Mobile Test Runs](https://testingbot.com/resources/courses/mobile-app-testing/debugging-failed-runs)
10. [10 Knowledge Check](https://testingbot.com/resources/courses/mobile-app-testing/knowledge-check)

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

 Chapter 10 of 10 Beginner 7 min read Updated Nov 2026 

# Knowledge Check

Ten questions on the decisions this course covered: where to run a test, which framework fits, how builds reach devices, and how to read a failure. Answer all of them, then check your answers at once.

1. A team wants feedback on every pull request within ten minutes and a release check on the phones their users own. Which setup fits?

 Real devices for every pull request, nothing before release Emulators and simulators on pull requests, a real-device matrix nightly and before release Only emulators, since they run the real OS Only one real flagship phone for everything

Virtual devices are fast and plentiful, which suits pull requests. Vendor skins, real hardware and performance only show up on real devices, so those runs belong before release, where a slower run is acceptable.

2. Which bug is an iOS Simulator least likely to reveal?

 A button that overlaps text on a small screen A wrong total in the basket A crash when a required field is empty The app being killed under memory pressure on an older iPhone

The simulator uses the Mac's memory and CPU, so it does not reproduce a phone's memory limits. Layout, logic and validation bugs show up there just as well as on a device.

3. Android developers want UI tests that run fast, need no explicit waits and live next to the app code. Which framework fits best?

 Espresso Appium XCUITest Maestro

Espresso runs inside the app's process and synchronises with the main thread, so it is fast and needs few waits. Appium needs explicit waits and is slower per command; XCUITest is iOS only; Maestro is black-box and lives outside the app code.

4. An Appium session on a real Android phone fails while installing the app. The same capabilities passed yesterday on a different device. What do you check first?

 The test's waits The `tb:test-result` call Which device and OS version the session got, and whether the build supports them Whether the build name changed

An install failure happens before any test step runs, so waits and result reporting are irrelevant. A pattern can land on an old OS or a different CPU architecture than the build supports.

5. Where does a CI job get the `tb://` id it passes to the Appium tests?

 From a constant in the test repository, updated by hand From uploading the build it just produced to TestingBot Storage in an earlier step of the same job TestingBot creates it automatically from the Git commit From the newest app in the dashboard

Uploading in the same job ties the test results to the build that was just made and never runs into the 60-day expiry. A hand-maintained id goes stale; the newest upload in the dashboard may belong to someone else's branch.

6. Your plan allows two parallel sessions and a script starts ten Appium sessions at once. What happens?

 Eight sessions are rejected immediately All ten run at once on shared devices The account is suspended Two start and the rest queue; clients with a short connection timeout may give up while waiting

Sessions beyond the limit wait for a free slot. The risk is on the client side: if the new-session timeout is shorter than the wait, the client reports an error even though the grid would have started the session.

7. An Espresso assertion fails with "Expected: with text: is "1,5" Got: ... text=1.5". The device ran in German. What is the most likely cause?

 A locale difference: the test or the app formats decimals differently from what the other expects The view could not be found The emulator is too slow The test APK is out of date

The view was found and shows 1.5, while the test expects the German decimal comma. Either the app ignores the locale or the test assumes it; both are locale bugs worth fixing deliberately.

8. A test passes when run alone but fails when the whole suite runs on the same device. What is the most likely cause?

 The device is faulty The parallel limit is too low State left by an earlier test, such as a logged-in user or stored data The framework version is too old

Order-dependent results point at shared state. Start each test from a clean app state so it does not depend on what ran before it.

9. Which TestingBot CLI exit code should make a pipeline retry the job automatically, rather than report failing tests?

 0 1 2 Any non-zero code

1 is a CLI or infrastructure error, where a retry can help. 2 means the tests ran and failed, which a retry would only hide; 0 is success.

10. A new app supports Android 10 and up and iOS 17 and up, and you have budget for six real devices in the release matrix. How do you choose them?

 The six newest flagships Six identical phones, to remove variables Whatever is free at the time of the run From your users' analytics: the most used models and OS versions, including the oldest supported version of each platform

The matrix exists to represent your users. The oldest supported versions catch compatibility bugs; newest flagships alone or random free devices leave the real user base untested.

Check answers

## Where to go from here[#](https://testingbot.com#where-to-go-from-here)

You now have a working picture of mobile app testing: which device answers which question, which framework fits which team, and how a run on a cloud device is set up, scaled and debugged. To go deeper in one framework:

- The [Appium with WebdriverIO course](https://testingbot.com/resources/courses/appium-webdriverio) builds a full suite with locators, waits, page objects and reporters.
- The [Maestro course](https://testingbot.com/resources/courses/maestro) goes from first flow to tagged suites in CI.
- TestingBot's [Espresso](https://testingbot.com/support/app-automate/espresso) and [XCUITest](https://testingbot.com/support/app-automate/xcuitest) docs cover every option for native suites.

To earn the certificate, pass the exam and run the practical task on TestingBot.

[Previous · Chapter 9 Debugging Failed Mobile Test Runs](https://testingbot.com/resources/courses/mobile-app-testing/debugging-failed-runs)
## You finished Mobile App Testing: From First Test to CI

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 Mobile App Testing 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/mobile-app-testing/certification)
