-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
Affects Version/s: 4.0.2
-
Component/s: Test Optimization
-
None
-
Environment:
Clover 4.0.2
Ant 1.8
Java 1.8
TestNG 6.8.7
If I attempt to optimize my TestNG test run in an ant target like so:
build.xml snippet
<testng outputDir="./reports/intTest"
failureproperty="testNGFailed"
haltonfailure="false"
verbose="2"
workingDir="${base.dir}"
classfilesetref="int.tests"
listeners="com.atlassian.clover.ant.tasks.testng.CloverOptimizedTestNGSelector"
groups="clover-optimized">
<sysproperty key="clover.test.snapshot" value="path/to/clover.db.snapshot"/>
<sysproperty key="clover.initstring" value="i/dont/exist/.clover/clover.db"/>
<!-- ... -->
</testng>
where:
- path/to/clover.db.snapshot exists on the file system and is a valid snapshot file.
- i/dont/exist/.clover/clover.db does not exist on the file system,
then Clover prints the log message:
Clover is unable to optimize this test run because no Clover registry was not found at: 'path/to/clover.db.snapshot'
This is not correct - Clover logged the path to the snapshot file, but it actually could not find the coverage registry.