Just like insufficient culture is often a barrier to adopting DevOps, an inadequate testing culture can be a barrier to adopting the good testing processes that facilitate DevOps. But without discussing what testing culture actually looks like, or what facilitates it, it won’t improve—and neither will the issues surrounding the rest of the DevOps pipeline, which relies on well-tested code.

So what can be done to support behavioral change and build a culture that actively supports testing? To find out, we surveyed 300 developers, DevOps professionals and senior decision makers in companies in the US and UK that have at least partially adopted DevOps about their experiences with testing as part of DevOps, and their DevOps challenges more broadly.

We learned that common problems with DevOps often fall along a linear path, which starts with misunderstandings between the developers who work with code and their senior management, and ends in a testing bottleneck. 

Typically, that process looks like this:

  1. Differing opinions between developers and management about the quality of the company’s code and the efficiency of its SDLC lead to…
  2. Insufficient time and resources dedicated to testing from management, which leads to…
  3. Ineffective adoption of resource-intensive solutions to testing problems, which leads to…
  4. Manual testing as a key bottleneck in a CI/CD pipeline

The report breaks down the findings in each of these stages, and introduces a new maturity model we’ve developed based on the results to identify how organizations can start building a better DevOps testing culture.

The full results are out now in the 2020 Diffblue DevOps And Testing Report, which is also available with graphs and charts as a downloadable PDF on the same page. Hope you find the results useful!