Java Coverage Validator - Feature List

Java Coverage Validator has many useful features not found in other code coverage analysis tools.

Code Coverage

• Number of lines per file
• Number of lines visited per file
• Visit count per line
• Visit count per file
• Percentage of lines visited in each file
• Coverage statistics updated as the application executes
• Ability to sort the data for display
• Colour coded display for at-a-glance detection of files that have not been visited
• Source code display with line highlighting for editing source code and/or examining source code in situ with the statistics
• View coverage statistics in real time, as they change whilst your application executes

Data Views

• Coverage view. Shows coverage statistics on a file by file basis
• Functions view. Shows coverage statistics on a class-by-class, file-by-file, function-by-function, and functions-by-line-count basis
• File and line view. Shows coverage statistics on a file by file basis with the ability to drill down to each line and the source code for the line
• Diagnostic messages. For detecting unforseen errors in the instrumentation. If things are not behaving as you expect, the answer may be here

Data searches

• Object query
• Address query
• Function query
• Unvisited functions query
• Unvisited lines query

Automatic Merging

• Support for executing from the command line, allowing automated code coverage for all your regression tests. The command line also provides control over the HTML and XML export functions
• Support for session merging, so that multiple sessions can be merged to form an overall coverage score. This is vital for regression test support
• Interactive session merging. You can merge sessions using the user interface and view the results immediately
• Automatic session merging. As well as the command line and interactive merging, coverage results can be automatically merged into a dedicated session

Data export

• Coverage Data can be exported in HTML
• Coverage Data can be exported in XML

Startup

• Start by launching a process and injecting into that process at startup

Instrumentation

• Instrumentation is fast, a few seconds, not tens of minutes
• Two methods of instrumentation, with differing performance levels. A third (faster) method of instrumentation will be available soon

Java

• Uses JVMTI for use with recent JVMs.
• Uses JVMPI for use with older JVMs.
• Complete control is provided over choice to use JVMTI or JVMPI.

No need to rebuild

• No need to rebuild or relink your application

Miscellaneous

• Very configurable, almost all options are configurable by the user. Includes an option to reset to the default settings
  

Operating Systems

• Microsoft Windows Vista
• Microsoft Windows 2003
• Microsoft Windows XP
• Microsoft Windows 2000
• Microsoft Windows NT 4