We Don't Merge Red: Shifting E2E Tests Left in Mobile Development

There's a simple rule: the sooner a bug is found, the cheaper it is to fix.

Imagine a project where testing is only in production. The bug is discovered after the release. Our most profitable feature becomes unavailable. We lose revenue, waste time on debugging, fixing, and delivery - and along with that, time spent on postmortem and numerous incident-related calls.

Defect Correction Cost graph

Let’s move testing one step earlier - just before the release. The result: we don't release the product candidate with issues and fix everything early. The feature isn't broken. Our money flow isn't interrupted. Everything is great, but there's a catch.

If we find a critical bug during the testing phase, the development process starts over. We spend time reproducing, discussing, fixing, retesting, and delivering. The release is complete. All features are fine. The revenue keeps flowing. We’re safe.

But the problem of time management...

Copyright of this story solely belongs to hackernoon.com. To see the full text click HERE