QABattle

Mobile Testing / Quiz

Screen Objects: One Suite, Two Platforms

The mobile flavor of page objects: intent methods, per-platform locator maps, driver factories, and where the if-android-else-ios branching is allowed to live.

Difficulty
Easy
Format
Quiz
Points
100
Estimate
8 min

// MISSION BRIEF

Your Mission

A mobile suite that duplicates every test per platform rots in weeks. The screen-object pattern, page objects that also own gestures and waits, plus per-platform locator maps, is how one suite drives Android and iOS without drowning in ifs.

Six questions on structuring mobile tests for the long haul. Speed bonus active.

// FIRST CONTACT

Battle teaser

The screen object pattern is:

  1. AThe mobile flavor of page objects: each screen exposes intent methods (login(user, pass), openCart()) and hides locators, waits, and gestures inside
  2. BTaking a screenshot before every assertion
  3. CA design pattern only usable with Java
  4. DOne class containing every locator in the app
Answers, scoring, hints, and the full battle stay sealed.

// SKILL TAGS

appiumscreen-objectstest-architecturecross-platform