Reporting Coverage Analysis Results > Coverage Browser Report
The Coverage Browser reports include a report header and a summary of the packages in the snapshot. You can choose to include progressively more detailed information about the packages, classes, and methods in the snapshot. By default, the report includes data on all code in all packages. You can choose to exclude some code from the report using report filters.
You can include the following report options:
The Application Summary provides an overview of your application. For each package, it shows the total number of classes, methods, and lines of code and the percentage of each that were missed by your test suite. This summary is useful for communicating Coverage results to senior management.
Figure 1 Sample Coverage report header and application summary
The Package Summary breaks down the results in the Application Summary by package. For each class in a package, you get the total number of methods and lines of code in the package and the percentage of missed methods and lines. You can use this summary to get an overview of test case coverage. This summary is also useful as a management tool; you can assign classes with a high percentage of missed code to members of your team for further investigation.
Figure 2 Sample package summary
The Class Summary breaks down the results in the Package Summary by class. For each method in a class, you get the total number of lines of code in the method and the percentage of missed lines. A QA analyst might generate this report before investigating missed code and after modifying test suites. He can then use these reports to communicate before and after results to his manager.
You can add the source code to your report. For each method, the source code is displayed along with line numbers and whether or not the line was missed. This report is useful to have with you if you want to talk to a developer about a particular method. You may also find it useful for analyzing Coverage results away from the computer.
By default, the report includes data on all code in all packages in the snapshot. You can choose to exclude some code from the report using report filters.
To create a list of report filters:
1 Click an empty cell and enter the package, class, or method (no signature) in the cell. For more information, see the following subsection “Syntax for Filters.”
The first cell in the row indicates whether or not the filter is enabled.
2 Set the action to Include or Exclude the code from the report.
3 Add additional filters. If two filters refer to the same code, the filter lower in the table is used.
4 You can change your list of filters.
• To move a filter higher or lower in the table, drag the filter to its new location.
• To disable a filter, click the first cell in the row to change On to Off.
• To delete a filter, select the code, right-click, and select Delete.
Filters are case-sensitive and blanks are not allowed. You can use an asterisk (*) as a wild card; it matches any character, including the package separator. If you specify the code in a shorthand or partial form, JProbe automatically changes it to canonical form. The change may not be exactly what you desire, so be sure to verify it. JProbe does not check to see whether the filter actually matches anything in your code. For example, if you make a typing error in your package name, nothing in your code will match the filter and so the filter is not applied.
The following table contains common syntax and describes how JProbe interprets it: