Clover-for-Ant 2.5.0

11 May, 2009

Clover 2.5.0 Clover 2.5 is a major release with a key new feature called Distributed Per-Test Coverage, which will allow you to optimise your functional tests.

New Features

  • CLOV-391 Allow per-test coverage to be recorded across multiple JVMs.
  • CLOV-476 Commandline reporter should support Ant-style test inclusion/exclusion filter.
  • CLOV-393 Investigate runtime cost of recording per-test coverage and reduce it where possible.
  • CLOV-431 Scriptless integration for Ant builds.
  • CLOV-504 Instrumentation of type-parameterised test methods fail.

Improvements

  • CLOV-461 Clover Instrumenter should respect Ant's magic ant.build.javac.source property.
  • CLOV-468 Don't warn if snapshot is updated for a different clover.db location.
  • CLOV-500 Making retrotranslate optional if "notranslate" is passed as a property to the build.
  • CLOV-378 Remove duplicated ContextSets from the Clover model - saving serialization/deserialization time and reducing Clover's memory footprint.
  • CLOV-463 Allow a clover-merge to take a fileset refid.
  • CLOV-469 Allow clover-merge to update an existing clover.db.
  • CLOV-378 Allow per-test coverage data to be loaded from disk on demand rather than loaded into memory.
  • CLOV-361 Clover plugin is not available in IDEA 8 Milestone 1.
  • CLOV-362 Investigate clover-report performance improvements.
  • CLOV-391 Guard to ensure there is only one reconnection thread.
  • CLOV-408 Investigate coverage of assignment in a boolean expression.
  • CLOV-447 MethodInfo's throws and params fields are quite often empty arrays, use flyweight to reduce size of model in memory.
  • CLOV-475 Better debug logging when loading coverage.
  • CLOV-459 Allow CLI interface to accept whether coverage from failed tests is used during report generation.

Bugs

  • CLOV-515 SamplingPerTestCoverage loses some per test coverage if split over multiple .s files.
  • CLOV-438 Support method level-only instrumentation.
  • CLOV-471 Arguments aren't passed between test methods and synthetic Clover test methods resulting in compilation failures.
  • CLOV-367 2 x Test Optimization tests tend to fail randomly.
  • CLOV-509 Null values in PerTestRecordingTranscript during report generation.
  • CLOV-304 Unable to use Clover 1 license file with Clover 2, Maven plugin.
  • CLOV-467 AIOOBE during database load.
  • CLOV-428 Null Pointer exception thrown if initString points to a directory, not a file.
  • No labels