This is a regression in clover 2.5.0 . Clover 2.4.2 does not have this same problem.

The attached project reproduces this problem for both Ant and Maven2.
Both SubATest and SubBTest inherit from AbstractTest. The clover.snapshot that is generated after a test run contains only information about one of them. Which one is purely random. Which means that the problem eventually disappears when run enough times for each sub testMethod to be added to the snapshot.