Changes in Clover-for-Eclipse 3.3.0

March 31, 2014

This is a feature release with dedicated support for Spock framework and JUnit4 Parametrized Tests.

Please note that Clover-for-Eclipse plug-in does not support Groovy in the IDE (see the Supported Platforms page), so you'll have to use Clover's Ant, Maven or Grails plug-in in order to instrument Spock tests.

Implemented features and fixes

Please also see the Clover-for-Ant Changelog for all bugs fixed in the Clover product.

Known bugs

Changes in Clover-for-Eclipse 3.2.2

February 7, 2014

This release contains bug fixes for Java 8 and Grails 2.3. Please note that the Eclipse 4.3 (Kepler) does not support Java 8 yet. It's possible to use an Ant Builder with Clover-for-Ant, however.

Implemented features and fixes

Please also see the Clover-for-Ant Changelog for all bugs fixed in the Clover product.

Known bugs

Changes in Clover-for-Eclipse 3.2.1

January 10, 2014

This is a bug fix release.

Implemented features and fixes

Please also see the Clover-for-Ant Changelog for all bugs fixed in the Clover product.

Known bugs

Changes in Clover-for-Eclipse 3.2.0

October 21, 2013

This is a major release with support for Java 8. See Clover 3.2 Release Notes.

Implemented features and fixes

Please also see the Clover-for-Ant Changelog for all bugs fixed in the Clover product.

Known bugs

Changes in 3.1.12 for Eclipse

June 27, 2013

This is a bugfix release which addresses bugs found in 3.1.11 and earlier versions of Clover-for-Eclipse.

JIRA issue list

Please also see the Clover-for-Ant Changelog for all bugs fixed in the Clover product.

Changes in 3.1.11 for Eclipse

March 25, 2013

JIRA issue list

This release contains no fixes related directly with Eclipse plug-in. However, there were changes in Clover core - see the Clover-for-Ant Changelog.

Changes in 3.1.10 for Eclipse

January 8, 2013

This is a bugfix release which addresses bugs found in 3.1.8 and earlier versions of Clover-for-Eclipse.

This release contains fix of one Eclipse-related bug. Coverage reporting in source code editor is now more accurate - in case when branch expression is partially covered:

• source code will have red underline (*)
• left margin will contain marker in double colours "green/red" (**)
  

(*) previously, it worked only for coverage related with unit tests; now also for coverage not related with tests

(**) previously, partial branch coverage was not taken into account for margin coloring

JIRA issue list

Please also see the Clover-for-Ant Changelog for all bugs fixed in the Clover product.

Changes in 3.1.8 for Eclipse

13 November, 2012

This is a bugfix release which addresses bugs found in 3.1.7 and earlier versions of Clover-for-Eclipse.

Improvements

1) There are several new options available in the "Window > Preferences > Clover" tab.

Clover Plugin logging output level

New "Info" level is available.

Automatically open Clover views when enabling Clover on a project

When selected (default setting), Clover will automatically open four standards views ("Coverage Explorer", "Test Run Explorer", "Test Contributions", "Clover Dashboard") in the current perspective every time Clover is being enabled on a project (e.g. by right click on a project and selecting "Clover -> Enable/Disable on"). De-selecting this option is useful when you don't use some of Clover views and don't want to have them re-appearing.

Preserve instrumented sources in temporary directory

When enabled, Clover will keep a copy of every instrumented source file in the temporary directory (in Eclipse workspace). This allows to see the exact content of file which was passed to the compiler. Use this option for troubleshooting only, i.e. when you believe that code was incorrectly instrumented. Files will not be automatically deleted, so you'd have to clean temporary directory manually. When you enable this option, the "Clover Plugin logging level" will automatically switch to "Info". After every compilation you can find a message in Error Log view about location of instrumented files, for example:

CLOVER: Instrumented sources have been preserved in <workspace>\.metadata\.plugins\org.eclipse.core.resources\.projects\Moneybags\com.cenqua.clover.core\CLOV_INSTR_SRC

2) It's possible to define source code instrumentation level in the Project Properties window > Clover > Instrumentation tab:

Note, that the same option can be accessed from Coverage Explorer by left-click on a project:

Changing to the "method level" might be useful for very large projects in case when you need to know rough coverage only. The "method level" reduces Clover instrumentation overhead and thus reduces compilation time.

3) An alpha version of the Clover-for-Android (based on Clover-for-Eclipse) is available.

JIRA issue list

Please also see the Clover-for-Ant Changelog for all bugs fixed in the Clover product.

Changes in 3.1.7 for Eclipse

31 August, 2012

This is a bugfix release which addresses bugs found in 3.1.6 and earlier versions of Clover-for-Eclipse.

Improvements

Improved and corrected coverage reports in Eclipse IDE:

1. In case when per-test coverage is enabled, the pop-up shows correct hit count value (instead of 0 / 1).
2. The left ruler has the same orange colour as code background in case of coverage resulting from failed test.
3. The left ruler handles double colour in case of partial line coverage (green / red).
4. The left ruler handles double colour in case of partial line coverage related with failed test (orange / red / dark green).

The Coverage Explorer and Test Run Explorer views contain new button "Include coverage from passed tests only". It works in a same way as in IntelliJ IDE. When it's pressed, a coverage from failed tests equals is ignored - text editor shows hit count = 0, code is highlighted in red, percentage value in Coverage Explorer view is calculated for passed tests only.

The same action is also accessible from Coverage Explorer and Test Run Explorer context menu (opened by small triangle in top-right corner):

Clover-for-Eclipse will now protect you against accidental erasure of your source code  - when you try to put instrumented sources into one of source folders, the Clover dialog will show error message.

Manuals

We have prepared new manual how to instrument and test RCP Application under Eclipse IDE: Instrumenting+RCP+Application.

The new topic structure of Clover-for-Eclipse User's Guide has been established. We've added also 1. Clover for Eclipse in 10 minutes quick start guide.

JIRA issue list

Please also see the Clover-for-Ant Changelog for all bugs fixed in the Clover product.

Changes in 3.1.6 for Eclipse

19 June, 2012

This is a bugfix release which addresses bugs found in 3.1.5 and earlier versions of Clover-for-Eclipse.

Please also see the Clover-for-Ant Changelog for bugs fixed in the core Clover product.

Changes in 3.1.5 for Eclipse

25 April, 2012

This is a bugfix release which addresses bugs found in 3.1.4.

Please also see the Clover-for-Ant Changelog for bugs fixed in the core Clover product.

Changes in 3.1.4 for Eclipse

27 February, 2012

This is a bugfix release which addresses bugs found in 3.1.3.

Please also see the Clover-for-Ant Changelog for bugs fixed in the core Clover product.

Changes in 3.1.3 for Eclipse

17 January, 2012

This is a bugfix release which addresses bugs found in 3.1.2.

Please also see the Clover-for-Ant Changelog for bugs fixed in the core Clover product.

Changes in 3.1.2 for Eclipse

07 November, 2011

This is a bugfix release which addresses bugs found in 3.1.0. 3.1.0 was a major release that added support for Eclipse 3.6 & 3.7-RC and Java 1.7 language support (once Eclipse itself supports it).

Please also see the Clover-for-Ant Changelog for bugs fixed in the core Clover product.

Changes in 3.1.0 for Eclipse

31 May, 2011

This is a release which adds support for Eclipse 3.6 & 3.7-RC and Java 1.7 language support (once Eclipse itself supports it). A number of bugs have also been fixed in this release.