With almost every industry relying on high-quality software today, it is important that organizations keep in mind how they are going to deliver that software. SmartBear has released a report designed to look at how organizations are developing and maintaining the quality of their software in 2016.
“It shouldn’t come as a surprise that software quality is a top concern for organizations of all shapes and sizes,” said Justin Collier, product owner at SmartBear. “But heavy workloads, time constraints and lack of manpower plague many organizations. Despite the obstacles, however, with the right tools and best practices, teams can successfully and consistently peer review all code, leading to higher-quality software in less time and at a reduced cost.”
The “State of Code Quality 2016: Trends & Insights into Dev Collaboration” report found the No. 1 way organizations look to improve code quality is through code reviews, with 90% of respondents stating that code quality is the biggest benefit of code review, and 69% citing improving code quality as one of their biggest drivers for a code quality tool. Other ways respondents believe they can improve code quality included unit testing, functional testing, and Continuous Integration.
While nearly two-thirds of respondents are doing code reviews, a majority of developers use ad hoc or over-the-shoulder methods. The report found 71.9% of respondents are doing ad hoc, 63.4% do tool-based code review, and 52.8% do meeting-based code review.
“Beyond the quality of code, reviews are also viewed as a primary method for improving the ways teams work together, including sharing knowledge across the team, ability to mentor less-experienced developers, and increased collaboration,” the report stated.
The biggest obstacles when it comes to doing code review included workload, time constraints and manpower.
Other key findings of the report included Git and Subversion being the most commonly used software configuration management tools; using a tool for code review helps teams review code more frequently; and JIRA outpaces all other bug-tracking and requirements-management tools.