🔗Related Posts
Search...
⌘KThis project is discontinued - it's a demo. All data is fake and resets on refresh.
Pocketship
Priya Nair
4 days ago
Auto-quarantine + single retry is fine ONLY if quarantined tests page someone and have a deadline to fix. Otherwise the quarantine becomes a graveyard and you are back to ignoring red. Make flakiness visible, not silent.
Add a flaky-rate dashboard per test and fail the build if the overall rate creeps above a threshold. Treating flakiness as a tracked metric, not vibes, is what fixed it for us.
Most RN e2e flakiness I have seen is animations + implicit waits. Disable animations in the test build and replace sleeps with explicit waitFor conditions. Mock the network at the boundary so CI is not racing a real backend.