QABattle

Mobile Testing / Quiz

Waits on Mobile: Outlasting the Spinner

Implicit vs explicit waits through the Appium client, presence vs visibility mid-animation, and the two Android settings that delete half your flake.

Difficulty
Easy
Format
Quiz
Points
100
Estimate
8 min

// MISSION BRIEF

Your Mission

Mobile apps animate, spin, and lazy-load. Tests that find elements 200ms too early tap the wrong pixel or the wrong screen. Appium inherits Selenium's wait machinery, plus mobile-specific knobs of its own.

Six questions on waiting like you mean it. Speed bonus active.

// FIRST CONTACT

Battle teaser

driver.implicitly_wait(10) does what?

  1. ASets the HTTP timeout to the server
  2. BPauses the test for exactly 10 seconds
  3. CMakes every element find poll up to 10s for PRESENCE in the hierarchy; it cannot wait for visibility or a specific condition, and it applies globally to all finds
  4. DWaits for all animations to finish
Answers, scoring, hints, and the full battle stay sealed.

// SKILL TAGS

appiumwaitsflakinessmobile-testing