In the evolving landscape of software delivery, the lines between traditional quality assurance and site reliability engineering are blurring. While QA professionals have long been the gatekeepers of quality before releases, SREs have pioneered a different approach — one that treats reliability as an ongoing operational concern rather than a pre-release checkbox. The recent Ministry of Testing article by Simon Tomes and Marie Cruz asks a timely question: what can quality professionals learn from site reliability engineers?
The answer, it turns out, is quite a lot. Here are the key lessons that every software tester and QA engineer can borrow from the SRE playbook.
The SRE Mindset: Reliability as a Feature, Not an Afterthought
Site reliability engineers operate from a fundamentally different premise than traditional QA teams. For SREs, reliability is not something you verify at the end of a development cycle — it is a first-class feature that must be engineered, measured, and maintained continuously. This shift in perspective is perhaps the most valuable lesson for quality professionals.
When testers begin thinking of reliability as a product feature rather than a testing outcome, the entire approach to quality changes. Instead of asking “Does this pass the tests?”, the question becomes “How reliable is this system under real-world conditions?” This opens the door to production-informed testing strategies, chaos engineering, and proactive failure detection — all practices that SREs have refined over the past decade.
Observability: Moving Beyond Pass/Fail Testing
Traditional testing relies heavily on binary outcomes: tests pass or they fail. SREs, on the other hand, live and breathe observability — the practice of instrumenting systems so thoroughly that you can understand their internal state from external outputs. Logs, metrics, and traces form the three pillars of this approach.
Quality professionals can adopt this mindset by expanding their definition of “test results.” Instead of just checking assertions, consider instrumenting your test environments with the same observability tooling used in production. Tools like Grafana, Prometheus, and OpenTelemetry — traditionally the domain of operations teams — can give testers unprecedented visibility into application behavior during test execution. This makes flaky test investigations faster, performance regressions more visible, and edge cases easier to reproduce.
SLOs and Error Budgets: Data-Driven Quality Decisions
One of the most powerful SRE concepts is the Service Level Objective (SLO) paired with an error budget. An SLO defines the acceptable level of reliability — for example, 99.9% availability over a 30-day window. The error budget is simply 100% minus the SLO: the amount of acceptable failure. When the error budget is consumed, new feature development freezes until reliability is restored.
For QA professionals, this framework offers a pragmatic way to make risk-based testing decisions. Instead of testing everything equally, teams can use error budgets to prioritize testing efforts on the areas that most directly impact user-facing reliability. It also provides a shared language for conversations between development, testing, and product management about when to slow down and invest in quality versus when to push forward with new features.
Blameless Postmortems: Building a Culture of Continuous Learning
When incidents happen in production, SREs conduct blameless postmortems — structured analyses that focus on understanding systemic causes rather than assigning individual blame. The goal is not to find someone to punish but to identify process improvements that prevent recurrence.
This practice translates beautifully into the testing world. Testers who adopt the blameless postmortem approach when analyzing escaped defects create psychological safety within their teams. Instead of “How did QA miss this?”, the conversation becomes “What in our testing process allowed this to slip through, and how do we strengthen it?” Over time, this builds a learning organization where every defect becomes an opportunity for process improvement rather than a source of blame.
Bridging the Gap Between Testing and Operations
The convergence of QA and SRE practices is not about replacing one discipline with the other — it is about expanding the quality professional’s toolkit. By adopting observability practices, embracing error budgets, and fostering blameless learning cultures, testers can become more effective advocates for reliability at every stage of the software lifecycle.
As Tomes and Cruz suggest in their Ministry of Testing piece, the future of quality lies not in defending traditional boundaries but in cross-pollinating ideas between disciplines. The SRE community has spent years developing practical approaches to reliability at scale — approaches that testers can adapt and apply to their own work starting today.
Source: Staying fast, reliable, and usable — Ministry of Testing by Simon Tomes and Marie Cruz
Leave a Reply