Use this report to view a summary of the code review that was done on the source code and a list of the findings the code review produced. This report consists of the table in section one of the Score Card HTML report and the information in section three of the Complete HTML report.
The date and time that you ran the code review findings were exported into the report file.
The date and time that you ran the code review that the report is based on.
The code base on which the code review ran, for example, the workspace or a project.
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.
The number of files that were excluded from the report in the Code Review Export wizard.
The code review that was used in the analysis of the code base for the report, for example, the J2SE Best Practices code review.
The number of rules that were selected in the code review that ran on the code base.
The number of rules that were deselected in the code review that ran on the code base.
The number of findings with the Problem severity level.
The number of findings with the Warning severity level.
The number of findings with the Recommendation severity level.
The number of findings that were marked with an X in the Code Review view to signify that the match should be ignored.
This section provides details about the findings by category and by file.
Lists findings by rule category in the following format:
Lists the name of the rule category and the name of the code review it is in.
Indicates the severity level of the rule that was not adhered to.
Specifies the file where the code is located.
Specifies the line number in the source code where the finding occurs.
States the rule that was not adhered to and, therefore, produced the finding.
Lists findings by file name in the following format:
Lists the file name and all the findings it contains.
Indicates the severity level of the rule that was not adhered to.
Specifies the file where the code is located.
Specifies the line number in the source code where the finding occurs.
States the rule that was not adhered to and, therefore, produced the finding.