Code review findings

A code review finding is a line item in the Code Review view that shows code that is not compliant with the rules that were run. As a code review runs, the findings start to appear in the Code Review view. By default, all findings are grouped into the same rule categories as the rule the finding violated. However, you can configure code review to display the findings per source file.

After you run a code review, you are presented with a list of findings. A finding is not necessarily a problem, mistake, or bug. Consequently, you evaluate each finding in the list to determine how serious it is and which code, if any, to fix. The findings appear with the same severity (and category) as the rule that triggered it. You can change the severity of the rule.

Each finding contains the following information:

Example: The following example screen capture shows findings in the Code Review view. The list of findings is based on the rules in the Quick code review.

The screen capture shows the findings of the Quick code review that was run against the CodeReview_Examples project. The review consisted of 34 rules, and it was run against 103 source files. The review resulted in 40 findings of the severity Problem. The Cloneable category shows one finding that has a quick fix available.

Note the code review statistics below the tab, which provide detailed information about the code review: name, code base, number of rules and files included, and number and severity of the rules in the rule category that was run. The number shows how many occurrences there are in the file that do not adhere to the rule.

The following illustration shows all of the icons that can appear in a finding:

Terms of use | Feedback
(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.