QABattle

Mobile Testing / Quiz

Context Switching: Native, Webview, and the Void Between

Your locator is perfect. Your element is visible. Your test fails anyway, because you are in NATIVE_APP and the button lives in a webview.

Difficulty
Hard
Format
Quiz
Points
200
Estimate
11 min

// MISSION BRIEF

Your Mission

Hybrid apps split reality: native UI in one context, embedded web DOM in another, and Appium only sees the one you selected. Add chromedriver version matching and async webview registration, and you have the most-misdiagnosed failure family in mobile automation.

Seven questions. Speed bonus active.

// FIRST CONTACT

Battle teaser

driver.getContexts() on a hybrid app typically returns:

  1. AThe set of installed browsers
  2. BA list of open activities on the device
  3. C['NATIVE_APP', 'WEBVIEW_com.shop.app'], and commands run against whichever context is currently selected
  4. DCSS selectors available on the current page
Answers, scoring, hints, and the full battle stay sealed.

// SKILL TAGS

appiumhybrid-appswebviewmobile-testing