In the Snapshot Browser, JProbe displays results in terms of misses. A miss means that the code was not executed during your test cases.
The screen captures in the following procedure are taken from the Adventure tutorial. They are provided as an example only.
1 In the JProbe perspective, right-click a Coverage snapshot and select JProbe > Open Coverage Browser.
2 In the Coverage Browser, expand the package tree in the Application Tree panel (top panel).
3 In the % Missed Methods column, select a class that contains the highest percentage of missed methods. If you have to choose between classes with the same percentage, you may want to start with the one that contains the highest percentage of missed lines of code.
The methods in the class are displayed in the Method Detail table (bottom panel). You can show more columns by right-clicking and selecting Show/Hide Columns.
4 Choose a method to investigate. A good first candidate would be an interesting method with the highest number of missed lines.
Tip Generally speaking, you can ignore the results for <init>() methods. If you were to examine the code, you would find that initializations (such as InputStream inputStream = null;) are reported as missed. This result is due to how the compiler identifies the lines in its line data table. For more information, see Learning More About Coverage Results.
5 To view the source code, double-click the method. You may be prompted to locate the source code file.
If you have the source code, a Source view opens with the code displayed. By default, missed statements are displayed in red text and missed conditions (if tracked) in gold. Lines of code that were exercised by your test suite are in black text. Lines with no data are in gray. If you are filtering out catch blocks, these are displayed in gray as well.
Along the right margin is a navigation aid called the Coverage Bar. The length of the Coverage Bar represents all the source code in the file, not just the code currently displayed in the view. The colored stripes on the bar represent the relative size and position of missed lines of code and missed conditions (if available). You can click a stripe to navigate to that block of code or use the arrows at the top of the bar to move to the previous or next missed code. For more information, see Exploring the Coverage Source View.
6 Determine if the missed lines of code in the method require testing and adjust your test cases. You may need to consult the software developer in charge of the code. If so, you can print a report of your results.
7 If you want to review all missed code in this source file, click the Next Stripe arrow on the Coverage Bar.
The view scrolls to show the next missed line.
8 To investigate a missed method in another source file, select the Snapshot Browser tab and repeat the above steps.
9 When you are done, use the full version of JProbe to rerun the session with the improved test cases.
As your program grows and evolves, your test suites need to keep pace with the changes. Changes are not always communicated to QA analysts. After you have achieved a satisfactory level of coverage, you can continue to use the JProbe Coverage analysis tool regularly. If your percentage of missed methods or missed lines of code goes up, it is an indication that development has added new code that is not covered by your test cases.