76 articles on Testing for iOS performance
Showing 20 of 76 articles (Page 2 of 4)
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.
Cash App just open-sourced Turbine 1.0, solving one of the trickiest parts of Kotlin coroutines: testing Flows without the headache.
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.
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?
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?
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.
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.
Turo's iOS team took their crash-free rate from 99% to 99.99% in just one year. Here's how a lean 5-engineer team achieved what most would consider impossible.
Lyft's iOS tests were spending 93% of their time on steps that had nothing to do with what they were actually testing. Sound familiar?
Instawork runs over 1 million tests daily in their CI pipeline. Here's how they made unit testing a core engineering practice, not an afterthought.
Swiggy was drowning in analytics chaos. Thousands of events per session, scattered specs across docs, and manual verification eating up engineering time.
Very Good Ventures shows how to build a production-ready Flutter app with Supabase that achieves 100% test coverage. This isn't your typical Firebase clone tutorial.
Slack's engineering team ran into a classic performance testing problem: spinning up load tests was so time-consuming that teams avoided doing it. Their solution? Never stop testing.
Tokopedia's iOS team was drowning in 30-minute unit test cycles with 65 developers fighting over 9 CI/CD machines. They cut that time by 8X.
Grab's iOS team turned flaky CI tests into a 50% CPU reduction story. Their secret? Observability tools and some creative workarounds for Xcode 13.1's notorious Spotlight bug.
New OS releases can break your app overnight. The React Native team shares critical changes in iOS 15 and Android 12 that could impact your users.