Detox.

Where Detox fits on a long engagement.

Grey-box is the design decision that matters. Because Detox can see network requests, timers and animations from inside the application, it knows when the app has actually settled. Black-box tools have to poll and guess, which is why they need explicit waits and why those waits are where flakiness lives.

It is still end-to-end testing, with the costs that implies: slow relative to unit tests, and dependent on a simulator or emulator in CI. The right coverage is a small number of genuinely critical journeys, not a broad suite. Teams that try to test everything this way end up with a pipeline nobody waits for.

What an assigned team does with Detox.

End-to-end suites decay faster than any other test type because they touch everything. A UI change three layers away breaks a test that was not about that screen at all, and without ownership the response is to disable it.

That ownership is a named responsibility rather than a shared assumption, which is why it is assigned as dedicated outsource qa testing capacity rather than expected of developers between features.

What we use Detox for.

• Critical journeys verified end to end Sign-in, purchase and onboarding tested on both platforms from one suite.
• Stability without explicit waits Synchronisation from inside the app, which is what keeps the suite green for the right reasons.
• A suite fast enough to gate releases Deliberately narrow coverage, so the pipeline stays something people wait for.

How Detox capacity is assigned.

End-to-end mobile coverage is kept deliberately narrow so the pipeline stays fast, and it is scoped alongside the mobile development capacity rather than after it. What that covers is set out in how the monthly fee is built.