Start here

Home
About Klocwork
What's new
Fixed issues
Release notes
Installation

Reference

C/C++ checkers
Java checkers
C# checkers
MISRA C 2004 checkers
MISRA C++ 2008 checkers
MISRA C 2012 checkers
MISRA C 2012 checkers with Amendment 1
Commands
Metrics
Troubleshooting
Reference

Product components

C/C++ Integration build analysis
Java Integration build analysis
Desktop analysis
Refactoring
Klocwork Static Code Analysis
Klocwork Code Review
Structure101
Tuning
Custom checkers

Coding environments

Visual Studio
Eclipse for C/C++
Eclipse for Java
IntelliJ IDEA
Other

Administration

Project configuration
Build configuration
Administration
Analysis performance
Server performance
Security/permissions
Licensing
Klocwork Static Code Analysis Web API
Klocwork Code Review Web API

Community

View help online
Visit RogueWave.com
Klocwork Support
Rogue Wave Videos

Legal

Legal information

Comparing two builds in Klocwork Static Code Analysis

Comparing two builds in Klocwork Static Code Analysis

You can compare two builds using a specific search syntax in Klocwork Static Code Analysis. This allows you to see what changes have occurred between those two builds (for example, to see what issues have been fixed between builds).

When should you compare builds?

Typically, the build comparison would be most helpful in two situations:

  • You have upgraded to a new version of Klocwork. We recommend running your final pre-upgrade analysis and your first Klocwork 2018.1 analysis on identical source code, and then comparing the two builds, so that you can properly assess the changes in your analysis results due to improvements in our analysis engine. For details on improved, added and removed checkers in this version, see What's New.
  • You want to compare your current build with a milestone build (such as a recent product release)

For other comparisons, reports probably better suit your needs.

Using the build comparison syntax

  1. If you're not already viewing the Projects list, click Projects at the top left.
  2. Locate your project in the list and click the New or Open issues link.
  3. In the Search for field, use the following syntax:
    diff:<build1>,<build2> [state:New|Fixed|Existing]
    
    The order of specifying the builds doesn't matter. If the build name contains spaces, you must surround it with quotation marks.

Examples

If you simply specify two builds, you see a list of all issues that exist in both specified builds:

diff:build_1,build_5

Using the keyword state with New, Fixed or Existing filters the list of issues by state. This example shows you all issues that have been fixed between build_1 and build_5:

diff:build_1,build_5 state:Fixed

You can also use the keyword last to compare a specific build to the most recent build:

diff:build_3,last