82 articles on Testing for iOS performance
Showing 20 of 82 articles (Page 3 of 5)
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.
Victoria Gonda from Square tackles a tricky KMP problem: Kotlin/Native doesn't support I/O, yet your shared tests need to read fixture files. Here's the workaround that makes it possible.
Revolut's iOS team ships weekly updates with minimal regression. Their secret? Making unit tests actually fun to write.
Microsoft Teams Mobile merges 50+ commits daily from 350+ developers. How do they catch performance regressions before users feel the pain?
Grab's logging bills were spiraling out of control. Their solution? A complete rethink of how they capture what happens in production.
Adrian Russell from Just Eat Takeaway turned on Screen Curtain and tried to order food through his own app. What he discovered was shocking: over 100 accessibility failures making the app nearly impossible to u...
Pinterest's UI test suite was failing more than 50% of the time. Engineers were drowning in false positives, and tests had lost all credibility.
Walmart's DevOps team has a bold claim: if you're not testing during development, you're risking the business. Here's why your testing strategy might be fundamentally broken.
Spotify cut iOS pre-merge CI times by 75% with one infrastructure change. Here's how they validated and scaled their approach.
Trevor Phillips from Freeletics built a comprehensive GPS testing framework that improved location accuracy from 7% error down to 1.68%. Here's how they systematically validated every improvement.
Julio Zynger from SoundCloud reveals how they ship mobile releases every two weeks without breaking things. Their secret? A release train model that turns chaos into predictability.
Shopify's iOS team ships hundreds of commits weekly to a monorepo. Their testing strategy keeps quality high without slowing down velocity.
Matthew Healy from SoundCloud reveals how a single integration test can catch memory leaks across an entire VIPER module. Unit tests alone won't save you from the sneaky leaks hiding in object interactions.
Kateryna Sprynsian from Bumble's QA team shares a hard truth: when iOS 12 dropped, 60% of their users updated within weeks. Were they ready?
Kateryna Sprynsian from Bumble Tech shares a hard truth: when iOS 12 launched, 60% of their users updated within 8 weeks. Were they ready? Here's how they avoided disaster.