Discover 167 articles on Testing in mobile performance
Showing 20 of 167 articles (Page 3 of 9)
Skeelo's QA team built a scalable E2E testing framework using Python + Appium. Here's the architecture that keeps their mobile tests maintainable as the app grows.
GitHub's iOS team just cut their CI testing time by 60%. Here's how they did it with Apple Silicon runners and some smart architectural changes.
Uber's mobile testing was broken. Engineers spent 30-40% of their time maintaining test scripts that broke with every UI change. So they built an AI that tests apps like a human would.
Duolingo catches critical bugs before users ever see them. Their secret? 70% of employees actively use internal builds daily.
Uber deploys 11,000 code changes weekly. How do they catch crashes before users notice? They built Healthline, powered by Apache Pinot.
Adrian Prantl, Augusto Noronha, and Dave Lee from Apple's Debugger Compiler Integration team just made debugging Swift apps significantly faster. If you're still using the old `p` and `po` commands the same way...
Handshake's iOS team just eliminated nearly 3,000 lines of testing and demo code. Their secret? Rethinking how they do snapshot testing.
Joana Melo from Klarna turned a 6-month diversity program into company-wide impact by solving a pain point that had defeated multiple engineering teams before her.
Dream11 cut regression testing from multiple days to just one hour. Here's how they rebuilt their entire mobile automation framework from scratch.
Cash App just open-sourced Turbine 1.0, solving one of the trickiest parts of Kotlin coroutines: testing Flows without the headache.
Emre Muhammet Engin from Getir tackles a truth bomb: if your code is hard to test, your design probably sucks. His deep dive into MockK shows Android developers how to fix that.
Glance's engineering team scaled their load testing from basic scripts to a full Kubernetes-powered distributed system. Here's how they did it with Locust.
AWS Device Farm now supports rooted Android devices, unlocking granular performance benchmarking that was previously impossible at scale.
Premise's mobile team caught a sneaky 3x build time regression that only showed up in CI. Here's how they hunted it down using Gradle Enterprise.
You found the jank in your Android app. Now what? Most teams stop at identifying the problem—but that's only half the battle.
Aliou Sarr from leboncoin reveals how shifting UI test ownership from QA to developers doubled their test count in under a year. The result? A 99.6% crash-free iOS app serving 28 million monthly users.
Swiggy was missing production deadlines because their UAT environments were constantly unstable or unavailable. Sound familiar?
Glance's engineering team serves 100M+ users where visual experience is everything. When UI performance drops, users notice immediately—and they leave.
Spotify Wrapped serves 150M+ users in a single morning. How do you load test for that kind of thundering herd?
Gojek's engineering team cracked a common CI/CD headache: how do you run automated tests from a separate repo without creating pipeline chaos?