Coverity Static Analysis

Coverity Static Analysis helps increase developer productivity by finding and fixing defects faster, increases visibility into defect history within and across projects to stay on-schedule and make better fix/no fix decisions, and reduces the risk of product quality issues in the field.

Best of Breed Analysis Engine

Why is Coverity´s analysis engine unique?
It understands and thinks about your code like a person would, not a machine.
How does it do this?
1. Breadth of coverage: it looks for many different types of defects in your code and looks for the same problem in multiple ways.
2. Coding behavior: it takes the developer's coding behavior and intent into consideration, understanding what you meant to say, not what you said.
3. Continuous tuning: it leverages all of the information collected from scanning trillions of lines of code from commercial customers and the open source community to tune the analysis engine.
This guidance helps you quickly find what happened and where it happened so you can save time, fix more bugs faster, and improve your coding skills.

100% Code Coverage
Coverity Static Analysis provides the deepest level of granularity to help find every bug, across every line of code, with evidence of existence, and without the need to build any test cases. It even exposes unreachable areas of the code due to logic errors.

Boolean Satisfiability (SAT Solver)
This innovative technology suppresses defects that could not possibly have occurred by executing and pruning out the infeasible paths, providing a low false positive rate without trading off false negatives.

Interprocedural Analysis
Many errors can only be found by crossing function boundaries. This analysis technique looks at all of the functions in context to find the defect, goes to an infinite number of levels deep to tell you where the problem is, and shows you the exact location in the code that was analyzed to provide evidence of the problem.

Statistical Analysis and Programmer Intent
This Coverity patented technique looks for patterns, reporting when there is a deviation from the pattern. The analysis engine recognizes programmer intent, not just code semantics, by following user behavior.