113 articles on Testing for Android performance
Showing 13 of 113 articles (Page 6 of 6)
Rajdeep Varma from Badoo cracked a problem that's plagued mobile test automation for years: Calabash could only test what's inside your app, while Appium couldn't use backdoor methods. His solution? Merge the b...
Alexander Khozya from Bumble's mobile QA team shares battle-tested strategies that caught critical bugs before millions of users did. His team's approach to testing saved them from costly re-submissions and use...
Rajdeep Varma from Badoo (now Bumble) tackled a problem that sounds impossible: running Android device tests inside Docker on macOS when Docker can't even see USB devices. The workaround? Brilliantly hacky.
Twitch discovered that Google Play's staged rollouts create biased user groups, breaking standard A/B testing assumptions. Here's how they adapted.
Klarna Engineering found that developers' optimism about their own code creates predictable load testing blind spots. Here are the four mistakes that keep biting teams before Black Friday.
Facebook built a 2,000-device testing lab inside a data center. The journey from tangled cables to custom EMI racks is a masterclass in scaling mobile performance testing.
Abha Gupta from Walmart Global Tech tackles one of Android testing's toughest challenges: running mock servers inside your APK for reliable device farm testing. No external dependencies, no flaky tests.
Still manually checking code coverage on Android PRs? There's a better way that turns coverage tracking into an automated gatekeeper for your codebase.
Skyscanner's test suite had a 99% pass rate. Sounds great, right? Wrong. Those false failures were costing hours of productivity and masking real production issues.
Tommy MacWilliam from Quora reveals how they A/B test mobile UX without waiting weeks for App Store approval. The secret? A hybrid architecture that lets them iterate at web speed.
LinkedIn ships a single mobile binary but runs dozens of A/B tests simultaneously. Here's how they pulled it off without constant app releases.
When mobile traffic jumped from 25% to 40% in six months, Etsy knew they had a problem. Their engineers were testing on personal iPhones while users browsed on dozens of different devices.
Twitter's iOS team shipped beta builds to employees and discovered crashes that would never show up in testing. The culprit? Jailbroken devices and unprefixed Objective-C categories.