Coverage tool: improve support for execution environments with custom class loading #149

rliesenfeld opened this Issue Mar 9, 2015 · 0 comments


None yet

1 participant


Certain testing tools (PowerMock, Robolectric) create copies of classes through a custom class loader.

The coverage tool currently won't instrument classes whose names have already been registered as instrumented; this check should also account for different class loaders.

Also, if classes get "reloaded" without a complete ProtectionDomain, they won't be considered for coverage. This situation should also be checked for, so the reloaded classes still get instrumented.

@rliesenfeld rliesenfeld self-assigned this Mar 9, 2015
@rliesenfeld rliesenfeld added a commit that closed this issue Jul 17, 2015
@rliesenfeld rliesenfeld Enhancement: added support for measuring the coverage of classes load…
…ed or reloaded by a custom class loader; closes #149.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment