Last week, we announced the latest release of the Coverity Development Testing Platform, and I shared some of the features and enhancements related to improving your time to market. Today I want to discuss the second key area of focus for this release, lowering risk. If you read the blog last week, you may recognize some of these features because this release is focused on both improving time to market AND lowering risk, so many of our new features were designed to provide benefits in both areas.
- Last week, I discussed the new test prioritization feature in Coverity Test Advisor which helps prioritize the order in which tests should run, based on code criticality and risk, change impact and project priorities. This means development teams can maximize their limited testing windows and align testing to where the risk is in the code.
- Coverity Policy Manager allows you to define and enforce a consistent standard for code quality, security and testing across your organization. As I mentioned, you can fully customize your views with heat maps and other charts for early warnings of violations and risks. In addition, you can drill down from the warning in Coverity Policy Manager to the specific issue in Coverity Connect, so issues can easily be triaged and managed. This allows you to establish a stage gate to ensure that the product is not promoted to the next phase of the lifecycle unless all violations and risks have been properly addressed.
- Coverity Quality Advisor and Coverity Security Advisor include enhancements that help lower risk as well. We introduced new quality checkers for C, C++ and Java and improved accuracy for existing checkers. We also improved C++11 support and expanded detection of OWASP Top 10 and CWE Top 25 issues for Java.
To learn more about how the new release of the Coverity Development Testing Platform can help you improve time to market and lower risk, register for our upcoming What’s New in Coverity 6.6 webinar.
The post 3 ways Coverity 6.6 helps you lower risk appeared first on Software Testing Blog.