Changes in 2.5.0 for Eclipse
11 May, 2009 - Build 20090511
Clover's much-lauded feature called Test Optimization is now available in Clover for Eclipse, bringing the ability to run only the tests that have been affected by changes to program code. In many cases this will cut down the running time of your test phases and allow you to run them far more often. The full Eclipse version number for this build of the plugin is 2.5.0.v20090511090000.
新機能
Add Test Optimization for Clover for Eclipse. |
|
Allow users to instrument at the statement or method level on a per-project basis. |
|
Allow users to turn off tracking of per-test coverage. |
|
Add source annotations to display coverage by failed test. |
|
Make default flush setting "interval" or "threaded" if the project has a web or j2ee project nature. |
改善点
Improve performance of Coverage Explorer. |
|
Add manifest entries to make clover-runtime.jar a J2EE optional library. |
|
Have a default user specified initstring. |
|
Warn users if enabling too many projects at once that this may cause Eclipse instability. |
|
Default test filter should include classes both ending and beginning with Test in the name. |
|
Rename log setting of "minimal" to "none" and make Clover stop logging to the Eclipse log when this is enabled. |
|
Allow users to choose if per-test coverage data is loaded into memory. |
|
Allow relative initstrings that resolve to files outside of the project. |
|
Add special source annotation for code where both branches aren't covered. |
|
Integrate all Clover views with main Eclipse perspectives. |
|
Allow a way to debug memory exhaustion in forked reporting. |
|
Allow aggregated and non-aggregated coverage modes. |
|
Added example excludes pattern. |
バグ修正
Automatic full builds that aren't clean builds cause coverage to be 'forgotten'. |
|
NPE reported constantly in Error Log. |
|
Test Contributions view does too much work when not visible. |
|
Eclipse with Windows + JRE 1.4 may fail to compile instrumented source because of long file names. |
|
No source annotations for files with encoding different to the project. |
|
Error marker "Coverage load failed: Background job" appears after enabling Clover or changing the initstring and is hard to get rid of. |
|
Plugin Startup is Slow and Throws Many Exceptions. |
|
Clover-enabled projects should always show in the explorers regardless of their load state. |
|
Snapshot should be discarded after N test runs not compiles due to frequent incremental compilations in IDE. |
|
NPEs in Test Run Explorer. |
|
Test Run Explorer not showing any children under projects. |
|
Missing package metrics incorrectly fall back to those for first encosing package in a given metrics scope. |
|
No default test source filter setting for new projects. |
|
Coverage annotation updates sometimes seem to get lost. |
|
NPE in test optimization when project does not have Clover nature. |
|
Memory leak in TestCaseInfo.Factory. |
|
Can't auto-open reports in Eclipse 3.2. |
|
Clover-for-Eclipse seems to be constantly ignoring certain method context filters. |
|
Forked reports should successfully complete regardless of whether there is coverage data. |
|
Forked reports do not respect "Include Failed Test Coverage" setting (it is always false). |
|
Test source folder settings ignored by HTML reports. |
|
Custom column definitions seem to be going missing on restarting Eclipse. |
|
New projects without source should not be flagged as Clover projects in an error state. |
|
Deleted projects still shown in Coverage Explorer. |
|
Forked reports don't respect "Ignore failed tests" setting. |