Page tree

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Open the report.html or report.pdf file saved to the working directory or location specified with the -report switch. Reports may contain different sections depending on the type of analysis, but the following sections are included in all static and flow analysis configurations.

Header

The following information is included:

  • Tool used for the analysis
  • Build ID
  • Test configuration
  • Time stamp of the analysis
  • Machine name and user name
  • Session tag
  • Project name
  • Number of findings with the highest severity
  • Number of failed tests

Static Analysis

The first part of the report covers the Static Analysis findings and is divided into two main sections.The first section is a summary which shows an overview of findings displayed as a pie chart. The colors indicate different severity types and their corresponding number of findings detected during static analysis:

The second section shows the details of static analysis findings. It starts with a table which includes static analysis results:

The following information is included:

  • Name of module
  • Number of suppressed rules
  • Total number of findings
  • Average number of findings per 10,000 lines
  • Number of analyzed files
  • Total number of files in the module
  • Number of code lines analyzed
  • Total number of code lines in the module

All Findings

The All Findings section displays the details of findings organized by category or severity. Click the Severity or Category link to toggle between views.

In the Category view, findings are reported by rule and grouped by category. A count of how many times each rule was violated in the scope of analysis is also shown.

In the Severity view, findings are reported and grouped by severity. A count of findings per severity is also included.

You can't toggle between these sections in the PDF versions of the report and they are published separately.

Findings by Author

This section includes a table of authors associated with the analyzed code and a count of findings per each author. Findings are segmented into findings associated with suppressed rules and findings recommended for remediation. Click on an author link to view their finding details.

The details view includes the following information:

  • File containing the finding and its location
  • Violation message and rule
  • Flow analysis reports also mark the cause of the violation (C), violation points (P), thrown exceptions (E), and important data flows (!)

Findings by File

You can navigate the analyzed code to the reported findings in the Findings by File section. Each node begins with a value that indicates the total number of findings in the node. The value in brackets shows the number of suppressed rules in the node. You can click nodes marked with a plus sign (+) to expand them. PDF versions of the reports are already fully expanded.{

Active Rules

The rules enabled during analysis are listed in the Active Rules section.

Metrics Summary

If your test configuration includes metrics analysis, a metrics section will appear in the report. See Metrics Analysis for additional information.

Test Execution

The second part of the report covers the Test Execution results and is divided into two sections.The first section is a summary which shows an overview of test failures and coverage displayed as pie charts:

The second section shows the details of test execution. It starts with a table which includes test execution results and coverage information:

The following information is included:

  • Module name
  • Number of unit test problems which need to be fixed
  • Number of exceptions which need to be reviewed
  • Number of assertion failures which need to be reviewed
  • Number of unit tests successfully executed
  • Number of unit tests failures
  • Number of incomplete unit tests
  • Total number of unit tests
  • Line coverage expressed as percentage

All Findings

The All Findings section displays the details of all unit test problems detected during test execution:

Findings by Author

This section includes a table of authors associated with the analyzed code and shows the total number of findings for each author. Click on an author link to view their finding details.

The details view includes the following information:

  • Finding location
  • Test name
  • Failure message

Executed Tests (Details)

You can view the findings in the Executed Tests (Details) section. The nodes where all the test passed are marked with "P" in square brackets. The nodes with test failures begin with a set of values in square brackets. The first value is a count of successfully passed tests and the second indicates the total number of tests executed in the node.The letter "F" indicates the final node where the test failed. You can click nodes marked with a plus sign (+) to expand them. 

Coverage

This section shows the details of coverage collected during the test execution. Each node starts with a set of values. The first value shows coverage expressed as a percentage. The second value is a count of the number of lines in the node which were covered during the test execution. The third value indicates the total number of lines in the node. You can click nodes marked with a plus sign (+) to expand them.

Test Parameters

The arguments specified during analysis are shown in the Test Parameters section

  • No labels