Discover 161 articles on Testing in mobile performance
Showing 20 of 161 articles (Page 3 of 9)
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?
BAM just launched Flashlight, a Lighthouse-inspired tool that finally brings performance scoring to mobile apps. Android developers now have a standardized way to measure app performance.
Swiggy's Android team was stuck in a painful cycle: rebasing PRs, waiting hours for full test suites to run, then doing it all over again. One frustrated engineer decided to fix it over a weekend.
John Flanagan from DoorDash reveals how his team eliminated duplicate code between SwiftUI previews and snapshot tests. The solution? An open-source tool that cuts testing boilerplate to a single line.
Lyft discovered memory leaks affecting only 1% of users—issues that would never show up in local testing. Here's how they built a production monitoring system to catch what profiling tools miss.
Strava's Android team hit a wall: testing server-driven UI meant wrestling with Charles Proxy crashes, EOF errors, and 3-4 minute build times. An intern decided to fix it.
Very Good Ventures shows how to build production-ready Flutter authentication in hours, not days. Their approach combines AWS Amplify with battle-tested architecture patterns for 100% test coverage.