Revision as of 21:14, 15 September 2020 edit Godin (talk \| contribs) 26 edits JaCoCo 0.8.6 ← Previous edit		Revision as of 00:58, 22 February 2021 edit undo Graeme Bartlett (talk \| contribs) Administrators 258,850 edits m mark file suffixes Next edit →
Line 217: * it is possible to dump or reset coverage data remotely and without a JVM exit. * does not require access to the source code and degrades gracefully with decreasing amount of debug information available in the input classes. * can instrument individual <code>.class</code> files or entire <code>.jars</code> (in place, if desired). Efficient coverage subset filtering is possible, too. * Makefile and ANT build integration are supported on equal footing. * The runtime overhead of added instrumentation is small (5–20%) and the bytecode instrumentor itself is very fast (mostly limited by file I/O speed). Memory overhead is a few hundred bytes per Java class.

Java code coverage tools: Difference between revisions