Test refactoring

The refactoring of the tests/code coverage while take a while. Today I removed some unused test classes and rewrote some tests.

More tests

Today I removed the unused classes from the project and started some refactorings in addition with new/more tests to improved test coverage.

Refactoring of preference/property page

As preference page and property page are very similar I changed the class hierarchy of the preference page (which extended FieldEditorPreferencePage in former versions). Both pages use OtherMoreUnitPropertiesBlock to create their UI now (DRY).

Patches

Tonight I integrated two patches which users of MoreUnit have mailed. Nice to see that there are other people who like to get involved :-)

Release 1.2.0

A new version of MoreUnit is available.

Preparing next release

Tonight I started to prepare the next release (1.2.X). After tagging I started to test. Therefore I created a new test workspace. In this workspace I created some different kind of projects (one/several test folders...) ans started to test.
Further testing is necessary. In addition a detailed test plan would be helpful.

Tests

Last week I rewrote all the test to get better code.
Yesterday I started to switch from JMock to EasyMock (because I am much more familiar with EasyMock). In addition I installed EclEmma to check code coverage. As a consequence I would like to increase test coverage before the next release.