How DevOps Impacts Testing

How DevOps Impacts Testing Lisa Crispin November 20, 2019

February 24, 2026 · 6 min read · Testing Guide

How DevOps Impacts Testing

Lisa Crispin

November 20, 2019

Early on in my programming career I memorize that it pays to make friends with the operations people and employment nearly with them. Back in the day, we depended on manipulator in the machine way to climb our tapes and hold our long batch line running smoothly. We needed the system administrator in the basement to keep our production environments healthy and do configuration changes for us. I much baked imp and visited the machine room and the cellar to share them. & nbsp;

Working with people of all specialties, whether or not they be actually on my development team, came course to me, I never felt siloed. In the 00s, we start let better creature that let all of us participate in maintaining continuous desegregation pipelines, adding automated regression test retinue, inquire build failures, checking log to try to understand production failure. I cooperate every day with our sysadmin, who expend time every day testing and automating tests. & nbsp;

Our unharmed squadtook responsibility for quality, and for get certain all testing activity got done for each narrative and feature before we delivered.Testing is a squad sport, not the province of a exam or QA team or someone.

In 2009, I read Continuous Deliveryby Jez Humble and David Farley. It is middling much all about quiz! I realized my own squad had be doing continuous delivery (CD) without apply that term. The book pull together all the practices and guides squad working towards CD. & nbsp;

2009 is also when we started hearing the term “ DevOps ”, after the maiden Devopsdays league in Ghent. The condition didn ’ t make a big wallop on me since my teams had operations and ontogenesis integrated already. But it helped me see that a lot of team, even team self-identifying as “ agile ”, were still throwing builds over the wall to operations teams to deploy and manage in production. & nbsp;

Whatever terminology you prefer, the culture, principles, and practices colligate with DevOps continue to influence how delivery teams approach testing. Let ’ s face at a few examples.

A holistic, whole-team approach

A whole-team approach to testing and edifice quality in is a central foundation of agile ontogeny. Many teams betray to construct the necessary relationships and break down the silo of strength. They may do some of the rituals around agile, like little iterations and day-to-day standups, but they yield to “ mini waterfall ” or go off the path to agile in other ways. & nbsp;

Logan Miles recently wrote that growth along the way. Rather than test to learn a set of exercise, DevOps puts the focus on the desired outcome: delivering small alteration to product safely and frequently. That focusing helps team address difficult challenges like construction partake understanding of stories and features among all team extremity to obviate re-work and shorten rhythm time. To get the confidence needed for CD and to foreshorten round time, teams learn to manoeuver development with technology-facing and business-facing test, automated regression test entourage and deployments, and other time-saving practices. This frees squad extremity up to do human-centric testing activities like exploratory testing and availability testing. & nbsp;

The whole-team approach to quality is backed up by data from several eld of results from the State of DevOps Survey. The book Accelerate, by Dr. Nicole Forsgren, Jez Humble and Gene Kim, reports that having reliable machine-controlled tests is a predictor of IT execution. This reliability is a result of developer taking responsibility for creating and maintaining acceptance examination - in collaboration with testers. & nbsp;

DevOps is all about take siloes. Freestanding test or QA teams are generally an anti-pattern. But we still need people with specific testing accomplishment, knowledge and experience embedded in cross-functional teams, building a quality DevOps culture together. Team extremity with these specialised capabilities support the team ’ s power to make testable code. They transfer testing acquisition across the team. They ask good questions, do risks seeable, contribute to the team ’ s uninterrupted calibre improvement. & nbsp;

DevOps advertize squad responsibility for the ware not only during growth but after release to production. We get more chance to learn operations-related skill. I oft see testing specializer conduct their turn in on-call rotations. They also aid try the on-call playbook and processes that help teams respond to production failure. Win/win/win. & nbsp;

The orbit of quality and examination is broaden to include infrastructure as well as tooling to discover about product use of our covering. Many testers and QA professionals are evolving to take on more of a trial consulting role on all these different panorama of testing, and further a test-first approach to infrastructure as code. & nbsp; & nbsp;

Test infrastructure autonomy

As the team I ’ ve worked on got control over our product ’ s infrastructure, and were empowered with new tools and technology such as cloud platforms and service, we were gratuitous to solve our own problems around test environments. Where we antecedently contended for too few exam environments in VMs on physical servers, now we could spin up both persistent and impermanent examination environments in the cloud, and deploy whichever version of our merchandise we wanted for testing. & nbsp;

SUSA automates exploratory testing with persona-driven behavior, catching bugs that scripted automation misses.

Our pipelines mechanically deploy builds from master/trunk or story subdivision to appropriate environments. We cognize when a new physique is ready to test, where it is deployed, and what code changes it bear

The cloud capabilities associated with DevOps enable teams to review test databases at will, add test data as needed, change the constellation of the application, re-start it when needed. We no longer have to wait around for sys admins to make modification for us, and task switch while we wait. We have more time for human-centric examination, and dependable test surround which we can control. This is a must for teams need to do continuous delivery. & nbsp;

Logging, monitoring, and observability

Cloud base and the power to store huge quantity of data cheaply base teams can instrument code to log every event in the application. We ’ ve had monitoring and alert tools for a long time now, but as data storehouse and substructure become more low-cost, we feature the ability to see exactly how customers are utilise our product. & nbsp;

The ability to safely test in product is expanding our testing attack. No examination environment can replicate production, and we can ’ t predict all the potential scenario real people will do. Teams can use techniques like release feature toggles to shroud new capabilities while they test them in production. A new range of products and tools are uncommitted to make it yet easier to do dark launching, canary launches and A/B tests. & nbsp;

Chaos engineering is a scary-sounding condition, but it ’ s a safe way to identify production matter before customers are regard. There are many requirement to make these character of experiments in product, like the ability to deploy new builds reliably and apace, good rollback strategies, enough logging and analytics and the ability to trace across distributed systems, effective monitoring and alerting. This is a unadulterated example of how DevOps has opened up new theory for try and improving product quality. & nbsp;

There are so many amazing analytics tools today. All of these capabilities mean we can track how mortal use our application and speck product job in a affair of seconds. & nbsp;

New risk-based approaches

Thanks to change in team civilization, infrastructure, and tools associated with DevOps, teams can mitigate risky region of their applications in multiple ways. We can assess each risk and decide how to prove it before and after deploy it to product. We can test a much larger and more wide varying range of scenarios. We receive more time for human-centric testing activeness such as exploring, accessibility testing, security examination. It ’ s easier to determine the impact of different production loads and stresses. & nbsp;

How is your team applying DevOps rule and practices? How can you use those to improve how you do your testing, occupy team members of all specialties in testing, and see more ways to build quality into your product? These are great theme for conversations with your speech team, including operations specialists. & nbsp;