You can use PureCoverage, in conjunction with a Java virtual machine (JVM), to analyze the coverage of Java applets, class files, JAR files, and Java code that is launched by container programs.
You can monitor Java code:
§ from PureCoverage standalone (start by specifying your JVM in the JVM tab of the Preferences dialog box, then run your code using the Run Program) dialog box
§ from the command line
With PureCoverage's PowerCov options (click Settings in the Run Program dialog box), you can choose whether to monitor the coverage of modules at line level or function level, or to exclude modules.
By default, PureCoverage uses the line level to monitor Java methods that are compiled to bytecode and for which debug data, which is stored in class files, is available. If debug data in not available for a module, PureCoverage excludes the module.
You can use PureCoverage's data analysis windows and tools to analyze the coverage data. For example, while code is running, you can monitor the status of its coverage, or pause and resume data recording. After you exit, you can filter out non-critical methods.
Notes:
§ For information about configuring your Java Runtime Environment for PurifyPlus, click .
§ PureCoverage uses Byte Code Insertion (BCI) technology to instrument Java code dynamically in memory as it collects code coverage data. Because of this, PureCoverage does not show instrumentation progress or save copies of instrumented files.
§ Some methods are always excluded. For example, native methods, classes that begin with java.*, com.ms.*, and sun.*, are always excluded.
(C) Copyright IBM Corporation 1993, 2010.