---
title: Knowledge check | Appium Tutorial with WebdriverIO
description: Nine questions on the decisions you make when writing Appium tests with
  WebdriverIO. Pick an answer for each, then check them all at once. 1. An old config…
source_url:
  html: https://testingbot.com/resources/courses/appium-webdriverio/knowledge-check
  md: https://testingbot.com/resources/courses/appium-webdriverio/knowledge-check.md
---

Course

[Appium Tutorial with WebdriverIO](https://testingbot.com/resources/courses/appium-webdriverio)

Chapter 8 of 8

1. [1 WebdriverIO and Appium Architecture](https://testingbot.com/resources/courses/appium-webdriverio)
2. [2 Learn about Appium](https://testingbot.com/resources/courses/appium-webdriverio/what-is-appium)
3. [3 Locate Elements](https://testingbot.com/resources/courses/appium-webdriverio/locate-elements)
4. [4 Implicit and Explicit Waits](https://testingbot.com/resources/courses/appium-webdriverio/implicit-explicit-wait)
5. [5 The Page Object Model](https://testingbot.com/resources/courses/appium-webdriverio/page-object-model)
6. [6 WebdriverIO Reporters](https://testingbot.com/resources/courses/appium-webdriverio/webdriverio-reporters)
7. [7 Running tests on TestingBot](https://testingbot.com/resources/courses/appium-webdriverio/tests-on-testingbot)
8. [8 Knowledge check](https://testingbot.com/resources/courses/appium-webdriverio/knowledge-check)

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

 Chapter 8 of 8 Intermediate 5 min read Updated Nov 2026 

# Knowledge check

Nine questions on the decisions you make when writing Appium tests with WebdriverIO. Pick an answer for each, then check them all at once.

1. An old config sets `deviceName: 'Pixel 8'` and `automationName: 'UiAutomator2'` without a prefix. Against Appium 3, what happens?

 Appium reads them as usual; the prefix is optional Appium converts them to `appium:` keys and logs a warning They are not recognised, so the session does not get the device or driver you meant

Only W3C standard capabilities such as `platformName` are unprefixed. Appium-specific keys need `appium:`, and WebdriverIO 10 also stopped treating unprefixed keys as a mobile session signal.

2. You installed Appium 3 with `npm install -g appium` and starting an Android session fails immediately. What is the most likely missing step?

 Appium 3 only supports iOS out of the box The UiAutomator2 driver was never installed with `appium driver install uiautomator2` Appium needs to be started with `--android`

Since Appium 2 the server ships with no drivers. Each platform driver is installed separately, and `appium driver doctor` checks its prerequisites.

3. Which locator is usually the best first choice for an element in a native app that must be tested on Android and iOS?

 An accessibility ID, written `~loginButton` in WebdriverIO A CSS selector such as `.login-button` An absolute XPath copied from Appium Inspector

Accessibility IDs work on both platforms, are fast and survive layout changes. CSS does not apply to native views at all, and absolute XPath is slow and breaks with any layout change.

4. After upgrading to WebdriverIO 10, `$('~inputA')` throws `StrictSelectorError` on iOS but works on Android. What is the right fix?

 Set `strictSelectors: false` in the config and move on Add `browser.pause(2000)` before the lookup Make the iOS locator unique, for example with a predicate string that also matches the element type

The error means the selector matched more than one element. Opting out hides the ambiguity again; a pause changes nothing. A unique locator fixes the cause.

5. Why is a global implicit wait discouraged in a WebdriverIO suite?

 Appium 3 removed support for implicit waits It only covers existence, slows down "element is absent" checks, and multiplies with explicit waits It makes every test fail if one element is missing

Implicit waits still exist, but WebdriverIO's auto-waiting and explicit `waitFor*` commands cover the same need with clearer behaviour. Mixing both makes timings unpredictable.

6. You need to wait until a loading spinner has disappeared. Which call expresses that?

 `await $('~spinner').waitForDisplayed({ reverse: true })` `await browser.setTimeout({ implicit: 10000 })` `await $('~spinner').waitForExist()`

`reverse: true` waits for the condition to become false. `waitForExist` waits for the opposite, and an implicit wait only affects lookups.

7. In a screen object, why define elements as getters (`get inputA() { return $('~inputA') }`) instead of storing `$('~inputA')` in the constructor?

 Getters are required by the WebdriverIO type definitions A getter builds a fresh reference when used, so it never resolves before the session exists or goes stale after an app restart Getters make element lookups run in parallel

Screen objects are imported before a session starts and live across tests. Lazy getters avoid stale or premature element references.

8. Your JUnit reporter writes files named `results-0-0.undefined.xml` for a native app run. Why?

 The JUnit reporter does not support Appium sessions `outputDir` is missing `outputFileFormat` uses `capabilities.browserName`, which is not set in a native app session

Build the filename from `cid` and a capability that is actually set, such as `platformName`.

9. On a cloud grid, real-device sessions sometimes fail with `UND_ERR_HEADERS_TIMEOUT` while the device you asked for is busy. Which config change does TestingBot recommend?

 `connectionRetryTimeout: 420000` and `connectionRetryCount: 0` `connectionRetryCount: 5` so the client keeps asking `waitforTimeout: 420000`

A queued device request can take up to about 390 seconds. The client must wait that long, and a retry would queue a second request rather than help. `waitforTimeout` only affects element waits.

Check answers

Next, put the page objects into practice at a larger scale in the [Page Object Model course](https://testingbot.com/resources/courses/page-object-model), or, if your team is also testing mobile apps with a declarative YAML approach, try the [Maestro course](https://testingbot.com/resources/courses/maestro). For day-to-day reference, keep the TestingBot [Appium options](https://testingbot.com/support/app-automate/appium/options) page open.

[Previous · Chapter 7 Running tests on TestingBot](https://testingbot.com/resources/courses/appium-webdriverio/tests-on-testingbot)
## You finished Appium Tutorial with WebdriverIO

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 Appium 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/appium-webdriverio/certification)
