Mobile App Automation for Dream11
Article Summary
Dream11 built a mobile automation framework that tests 100M+ user experiences across iOS and Android simultaneously. Here's how they eliminated duplicate test code and slashed regression cycles.
Dream11's engineering team faced a common scaling problem: every feature change required separate testing on both platforms, creating bottlenecks in their release cycle. They built a unified automation framework using Appium, Java, and TestNG to solve it.
Key Takeaways
- Single test codebase runs on both iOS and Android using Page Object Model
- Device allocation manager distributes tests across physical devices and emulators in parallel
- AI-powered Report Portal analyzes test flakiness based on historical execution data
- Jenkins CI/CT pipeline generates APKs and triggers automated nightly regression suites
- Backend health checks run before test execution to prevent false failures
Dream11 reduced maintenance costs and regression time by creating a cross-platform automation framework that reuses test code and runs distributed tests across their in-house device lab.
About This Article
Dream11's testing teams were using different automation frameworks for each user journey. This created redundant code that had to be maintained across multiple platforms, and every feature change required a full regression test.
Dream11 Engineering built a unified Mobile App Automation Framework with Java, Maven, TestNG, and Appium. They used a centralized Page Object Model design pattern that keeps all pages and locators organized in one place.
The framework let them reuse test code across iOS and Android. It cut maintenance costs by removing duplicate frameworks and made regression testing faster through parallel execution on multiple connected devices and emulators.