Insights from Recent State of DevOps Reports

Posted by John Emmitt on Jul 11, 2018

I've recently reviewed three State of DevOps reports from the past year, one from InterOp and two from Puppet-- the 2017 State of DevOps Report and the State of DevOps Market Segmentation Report. Here are a few excerpts and insights from these reports, particularly as they pertain to software performance testing as part of a DevOps environment.

The first, maybe minor, surprise is that while the majority (84%) of people know about DevOps, only a third of companies in the InterOp 2018 State of DevOps report have actually adopted it. However, an additional 35% expect to adopt DevOps within the next 12 months. So, 2018 is the turning point on adoption.

DevOps Implementation - 2018 Report

[Source: InterOp 2018 State of DevOps Report]

The Puppet Market Segmentation report looked at the question of where the DevOps journey started in the organization. Deployment automation was selected by nearly two thirds of respondents. Almost half (46%) cited Test Automation. Unsurprisingly, looking at it at the department level, Quality teams were more likely to start with Test Automation.

Starting with test automation makes sense when you consider that in the InterOp report, the number one driver for adopting DevOps was "the need to improve quality and performance of the applications."

 

InterOp report - Driver for DevOps

[Source: InterOp 2018 State of DevOps Report]  

In the InterOp report, 79% of DevOps teams reported improved quality and performance of their software. 35% said they achieved a "significant improvement."

The Puppet 2017 State of DevOps report found that high performance teams "are doing significantly less manual work" and have automated:

  • 33% more of their configuration management
  • 27% more of their testing
  • 30% more of their deployments
  • 27% more of their change approval processes

Performance test automation, from the standpoint of making test execution an automated part of the development cycle, can be achieved through integration with your Continuous Integration tool. Load testing tools like k6, integrate into your CI pipeline with tools such as GitLab, Jenkins, Circle CI, and Team City. (Learn more about GitLab integration by viewing our on-demand webinar). 

It's all about performance

In the Puppet report, they discuss their earlier findings on high performance teams: "In 2014, we first published our findings on how IT performance predicts organizational performance. We found that high performers were twice as likely to exceed their own goals for profitability, market share and productivity."

Performance testing tools are on the list of "Critical Tools to Enable DevOps" in the InterOp report, with 20 to 26% of respondents citing this. I'd suggest that this number should be higher given the importance of delivering higher quality and performance software. As more developers get involved in performance testing earlier in the dev cycle, the criticality of these tools will be more apparent.

Learn more about k6 and Load Impact by visiting our website.

 

Topics: DevOps, Performance testing, Load Testing

Recent Posts

Popular posts

Posts by Topic

see all

Subscribe to Email Updates