Its popularity has skyrocketed as businesses and consumers alike put more emphasis on the need to innovate and evolve regularly. After all, when was the last time you waited more than even six months for updates to the software you use? Would you even use software that required you to wait a year or more for a new version? Ten-plus years ago you would have. Today, not so much.
DevOps and Testing: Not Always an Obvious Match
For testers, the rise of DevOps has been an interesting ride. It’s raised a lot of questions about where testing fits into the DevOps lifecycle as well as the role of manual testing, as DevOps emphasizes automation. However, it’s time to ease these concerns.
First, testing isn’t going anywhere. Sure, testing might not be specifically called out as a stage in DevOps models, but that doesn’t mean testing doesn’t have a place in a DevOps world. Quite the opposite, testing fits in at every stage along the DevOps lifecycle. Perhaps the drawings in this point of view best represent that idea.
Second, manual testing can indeed be a part of DevOps. Contrary to popular belief, you can embrace DevOps without being completely automated. While automation may be important to DevOps, at its core, DevOps is all about continuous delivery. And if you can make that continuous delivery happen with manual testing, then you can still follow a DevOps model. Furthermore, manual testing remains critical for organizations, as it can often find more severe defects than automated testing can.
While testing — automated and manual alike — most certainly has a place in a DevOps world, testers do need to adapt in order to deliver the most value.
Here are five ways testers can do just that:
Embrace blurred lines: With the rapid deployments that characterize DevOps, the lines between production and pre-release environments are blurring. Testers can impact developers’ pipelines by being ready to validate software that’s in production. In other words, by testing software that’s in production, testers can become more like end users and analyze what’s actually going on, as opposed to solely what’s in development, to provide faster feedback.
Refer tests back to source code: In a DevOps environment, testers always need to refer tests and any issues uncovered back to source code. This referral notifies everyone of what’s happening in order to ensure alignment between testers and developers. Without this referral, testing results may not sync with the source code that goes into production. Furthermore, referring testing to source code also helps develop a strong business case for conducting testing.
Insert exploratory and session-based testing at different stages of the pipeline: Testers need to find ways to insert exploratory and session-based testing at different stages of the pipeline to ensure that testing doesn’t get lost in the shuffle of the rapid pace of development. Testers should emphasize that they are not trying to pump the brakes on development, but rather are launching exploratory sessions to jump into the environment in order to validate it and give feedback from an end user perspective before the software goes into production.
Make communication a priority: It may seem obvious, but we can’t overstate enough how critical communication is in the world of DevOps. With DevOps, you suddenly have cross-functional teams that own the full scope of a product, and that makes ensuring the entire team is on the same page critical to moving quickly (which is key to DevOps) and delivering the best possible final product.
Become well-versed in DevOps technology: By familiarizing themselves with some of the technologies that enable DevOps — such as Infrastructure as Code (IaC), which also requires testing — testers can gain a position of authority to hammer home the point that software hasn’t really been tested unless it’s been tested in the same environment in which it’s deployed.
Make the Value of DevOps Testing Obvious
At the end of the day, DevOps and testing might not always be an obvious match, but they are a necessary one. That said, testers can go a long way toward making this a more obvious and seamless match by adapting behaviors like those outlined here to add more value and to better demonstrate that value to the broader DevOps team.