At first glance, QA squad may not look to have much of a role to play in DevOps espousal. After all, DevOps (at least in the narrow, traditional sensation) is about developers and IT Ops team. So you might guess that developer and IT Ops technologist need to be the ones to spearhead DevOps adoption.

But I ’ d disagree. Due especially to the cultural antecedence that QA teams naturally comprehend, QA engineers, too, can play a critical role in spurring the adoption of DevOps within an organization.

Let me explain…

What count in QA culture

At the risk of be accused of rant generalizations, I don ’ t consider it ’ s too much of a reaching to say that most QA team prioritize the following:

• Automation: Virtually every modern QA team adopt test mechanization. It ’ s the only way to test at scale across a wide compass of environments.

• Holistic practices: The very nature of QA work take a focus not just on individual elements of an coating, but on how all of those elements interact. Sure, you might run tests against individual component of an app, but you likewise need to essay how those components interact.

• Collaboration: QA work is also collaborative by nature. The job of QA engineers is not just to find problems, but to collaborate effectively with people who can facilitate solve them.

Although there may be some variation out thither among different QA team, by and large, most espouse these three key cultural values.

QA culture and DevOps

Those three value happen to be key constituent in DevOps too.

Automation is critical for building an efficient, reliable delivery chain. A focus on the delivery concatenation as a whole, rather than individual pieces of it, is constituent of what defines DevOps. And collaboration, or the interrupt down of silo that separate different teams, is also part and parcel of what DevOps is all about.

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

It alone make sense, then, for QA teams to help lead the way toward DevOps for organizations that are working to assume it.

How QA can promote DevOps adoption

What might that look like in practice? Here are some specific ways in which QA technologist can steward DevOps adoption—or even become DevOps direct themselves.

Increasing automation

Your QA team might already be automating many of its tests. But it could work with developers and IT Ops to automate the handoffs that connect those tryout to the rest of the delivery grapevine.

For example, the QA team could help configure build tools so that new releases are automatically built when they pass exam. Similarly, it could integrate tests with developer & # x27; version-control systems in order to flag application components that fail tests.

By occupy the mechanization expertise that QA team already experience and expanding it to other areas of the covering bringing pipeline, your organization can move nigher to having a fully automated, DevOps-friendly delivery chain.

Collaborating around testing

Your QA team probably already collaborates with developers to help fix problems that are identified during package testing. But the quislingism may not be bechance in an efficient way. Here, QA teams receive an opportunity to help raise the communicating channels that fuel DevOps collaboration.

Those channels might vary reckon on the specific tools you take to use, but your QA engineers probably already have a sensation (from previous collaborations with developers) of what works and what doesn ’ t. Maybe you prefer to use Slack or similar messaging puppet to facilitate communication. Maybe regular face-to-face meetings employment best for your civilization. Or maybe you ’ ll choose to create new roles that bridge both maturation and testing.

Whatever the approach, the QA squad belike has lively, experience-based position to offer on how, exactly, to de-silo your organization.

Modeling shared ownership

At many brass, the QA team is more likely than former technical squad to have collective ownership of tasks. It ’ s rare for a peculiar QA engineer to “ own ” a specific package test; instead, QA team tend to write and run tests collectively.

For this reason, QA squad can serve as a model for other portion of the IT organization to adopt corporate possession. Developers who own individual pieces of code, or IT engineers who own sure servers or summons, can look to QA as a model of how to step aside from individual ownership and replace it with a framework of partake responsibility.

Conclusion

QA engineers need not be simple witness as your organization adopts DevOps. On the contrary, the QA team can ply all-important counsel for early appendage of the IT administration as they work to embrace automation, shared ownership of IT assets and a holistic approach to application delivery.

Chris Tozzi has worked as a journalist and Linux systems administrator. He has particular interestingness in open source, agile infrastructure and networking. He is Senior Editor of message and a DevOps Analyst at Fixate IO. His up-to-the-minute book,For Fun and Profit: A History of the Free and Open Source Software Revolution, was published in 2017.