🧪 I don’t trust a mobile feature until I’ve tested the failure case.
Happy-path testing is easy.
What matters is what happens when:
• the API returns 500
• the user goes offline mid-action
• a payment succeeds but the response is delayed
• a push token expires
• the app is reopened after 3 days
• a deep link points to missing content
• the same button gets tapped twice
• background sync fails silently
Most production bugs don’t happen when everything works.
They happen when one dependency behaves differently than expected.
That’s why for React Native apps, I like to test recovery behavior, not just feature behavior.