Mobile Testing / Scenario
The Session That Refused to Start
A first Appium test dies three times before a single tap: a removed client argument, a 404 on /wd/hub, and a server with no driver installed. Debug the whole chain.
- Difficulty
- Hard
- Format
- Scenario
- Points
- 200
- Estimate
- 13 min
// MISSION BRIEF
Your Mission
A new teammate copied a 2019 blog post to write the team's first Appium test in Python. Nothing has tapped anything yet: session creation itself has failed three different ways.
Read the code and the error log, diagnose each failure in order, then decide how to make session startup boring forever. Decisions are weighted.
// FIRST CONTACT
Battle teaser
First artifact
test_login.py (the attempt)
Attempt 1's TypeError happens because:
- APython 3 forbids keyword arguments named with underscores
- BThe Appium server rejected the connection
- CAppium Python Client 3.x removed desired_capabilities; sessions are built from typed options objects (e.g. UiAutomator2Options), which also emit the required appium: prefixes correctly
- DThe caps dict has too many keys for one session
Answers, scoring, hints, and the full battle stay sealed.
// SKILL TAGS
appiumcapabilitiesdebuggingci-cd