We Don't Merge Red: Shifting E2E Tests Left in Mobile Development — Programming Tech Brief By HackerNoon

Listen in the Podli app 🎧

Follow your favourite podcasts, listen offline and in the car with CarPlay and Android Auto, and always pick up where you left off. Free to try.

This story was originally published on HackerNoon at: https://hackernoon.com/we-dont-merge-red-shifting-e2e-tests-left-in-mobile-development.
A practical look at moving mobile E2E tests into pull requests, using Detox, CI gates, impact analysis, and QA review to catch bugs earlier.
Check more stories related to programming at: https://hackernoon.com/c/programming. You can also check exclusive content about #qa, #shift-left, #shift-left-testing, #e2e, #e2e-testing, #qa-automation, #detox-testing, #regression-testing, and more.

This story was written by: @eilinwis. Learn more about this writer by checking @eilinwis's about page, and for more stories, please visit hackernoon.com.

We made red e2e tests block merges. Tests now get fixed in the PR that broke them, not two weeks later during the release scramble. Getting there took impact analysis, parallelization, a stable main branch, and four months of convincing people. A PR run went from 60 minutes to 12, critical production bugs dropped by roughly half, and releases stopped being an event.