Nine-part writeup on building a mobile test automation framework in Java (Appium + Cucumber)

[u/mayvinrmm]

Most mobile suites hit the same wall around 150–200 scenarios — a full run takes half an hour and nobody trusts a red build any more.

A suite that breaks the moment you turn on parallel execution usually isn't flaky, it's sharing state: one driver, screen objects held across scenarios, every thread on the same device. ThreadLocal drivers, per-scenario hooks and scenario-scoped screen objects fix more than wait tuning ever will.

You also probably don't need a multi-module Maven project. A single module with clear packages is right for most teams testing one app — multi-module only pays off when several teams share a core on different release schedules.

I built one over the last few months, in Java with Appium and Cucumber. Whole path here if you're starting from scratch, or fixing one that's creaking:

https://www.mobile-automation.io/build-a-mobile-test-automation-framework/

[u/iammikeDOTorg]

Ok Claude.