Voidr
testingproductionstagingmonitoring

Testing in staging vs testing in production

If you still test in staging environments, deal with frequent rollbacks, and receive constant bug complaints, maybe the problem is trusting environments that don't reflect reality.

Victor Buchalla
Victor Buchalla
CTO & Co-founder
May 28, 20244 min

Testing in staging vs testing in production

If you still: → Test in staging environments → Deal with frequent rollbacks → Receive constant bug complaints

...maybe the problem is trusting environments that don't reflect reality.

Why testing only in staging no longer works

→ Test environments rarely replicate production complexity → Third-party integrations (Twilio, Clicksign, banks, etc.) rarely work the same → The confidence generated by these tests can be illusory — and dangerous

What we do at Voidr

→ We run thousands of tests directly in production, every day → We continuously monitor critical flows to detect failures before users → We structure intelligent fallbacks for external services → We run automated post-release tests → And we activate automatic rollback when detecting critical failures

The result

→ More reliable releases → Fast response to failures → Drastic reduction in end-user impact

The new goal

The new goal is not to avoid 100% of bugs in production. It's to ensure that, if they happen:

→ They affect as few people as possible → They're identified before support needs to tell you → And they're reverted before becoming serious incidents

Is your team spending energy on the same environment as your users?

Share article

Share this article with your network

Victor Buchalla
Victor BuchallaCTO & Co-founder

Victor is CTO & Co-founder at Voidr, where he leads quality and test automation initiatives for mission-critical systems.

Follow on LinkedIn

How much does each defect that escapes to production cost?

Personalized technical diagnostic. We analyze architecture and map improvement opportunities.

Request diagnostic