Trivago's mobile test framework evolved over nearly a decade, starting as an Appium 1 learning project to replace a broken homegrown setup. When Appium 2 deprecated the MobileElement pattern, the team chose a full rewrite rather than patching, redesigning around Appium 2's driver model with a plugin-based architecture, parallel thread execution (replacing multi-fork JVM processes), and clean platform separation for iOS and Android. Key improvements included lower resource overhead, safer extensibility, and a cultural shift where app developers now treat testability and accessibility IDs as first-class concerns during feature development. E2E tests now double as accessibility regression checks.
Table of contents
IntroductionThe Appium 2 (and later 3) TransitionWhat We Did Differently in the Appium 2/3 FrameworkConclusionClosing Thought526 Impressions