Complete HTML report

Use this report to see an overview of the status of your source code with a table that provides a summary of the code review information, and graphs that show percentages of code with findings by severity and code that did not produce findings.

1-Summary

Report file creation date

The date and time that the code review findings were exported into the report file.

Code review date

The date and time that you ran the code review on which the report is based was run.

Analysis scope

The code base that the code review was based on, for example, the workspace or a project.

Reported files

The number of files that were analyzed in the code review. This includes files with code review findings, and files that did not produce findings.

Filtered files

The number of files that were excluded from the report in the Code Review Export wizard.

Review applied

The code review that was used in the analysis of the code base for the report, for example, the J2SE Best Practices code review.

Enabled rules

The number of rules that were selected in the code review that ran on the code base.

Disabled rules

The number of rules that were deselected in the code review that ran on the code base.

Problems

The number of findings with the Problem severity level.

Warnings

The number of findings with the Warning severity level.

Recommendations

The number of findings with the Recommendation severity level.

Ignored

The number of findings that were marked with an X in the Code Review view to signify that the match should be ignored.

2 - Overview of the results

This section of the report corresponds to a set of metrics related to the analysis scope that you selected in the user interface when you ran the code review.

By category

This bar graph shows the number of findings by severity levels of Problem, Warning, and Recommendation for each rule category in the code review.

By severity

This metric provides a graphic score for the analysis scope. It shows the percentages of issues that were found in the complete analysis scope. The percentage of the most severe findings that were found in the analysis represents its score. The pie chart shows percentages of the most severe findings by file. The pie chart is partitioned into four groups by severity levels of Problem, Warning, and Recommendation, and the percentage of code that produced no matches.

3 - Additional information about the findings

This section provides details about the findings by category and by file.

3.1 - Sort review results by category

Lists findings by rule category in the following format:

Rule category name

Lists the name of the rule category and the name of the code review it is in.

Icon

Indicates the severity level of the rule that was not adhered to.

File name

Specifies the file where the code is located.

Number

Specifies the line number in the source code where the finding occurs.

Rule

States the rule that was not adhered to and, therefore, produced the finding.

3.2 - Sort review results by file

Lists findings by file name in the following format:

File name

Lists the file name and all the findings it contains.

Icon

Indicates the severity level of the rule that was not adhered to.

File name

Specifies the file where the code is located.

Number

Specifies the line number in the source code where the finding occurs.

Rule

States the rule that was not adhered to and, therefore, produced the finding.

Feedback
(C) Copyright IBM Corporation 2004, 2005. All Rights Reserved.