MoreUnit

MoreUnit 2.4.1 released

2011-03-26T11:26:00.004+01:00

We have released a new version of MoreUnit this week.
MoreUnit now has mocking support, which can be installed as a separate plugin.

With this release we relaunched a new website, thanks to Nicolas!

MoreUnit goes GIT

2011-03-16T17:08:00.002+01:00

MoreUnit is now available via GIT:

git://moreunit.git.sourceforge.net/gitroot/moreunit/moreunit

SVN will be dropped soon.

MoreUnit switched to Subversion

2011-02-24T20:45:00.002+01:00

The MoreUnit project switched from CVS to Subversion. The new repository URL is https://moreunit.svn.sourceforge.net/svnroot/moreunit
CVS is still available at the moment but will be dropped soon.
The reason for this switch is the long CVS downtime after the sourceforge attack. Perhaps this switch is only a first step, we are thinking about switching to GIT.

MoreUnit 2.3.0 released

2011-02-20T15:25:00.000+01:00

Package is now shown when user is prompted for selecting a class (Jump and Run actions)
Fix: exception when moving class to non-source folder
Fix: exception when jumping action had delay
Minor fixes

Sorry for not answering to blog comments

2011-01-31T21:00:00.002+01:00

Today I realized that I don't get a mail, if someone posts a comment to one of the blog entries and that's why I missed that some people commented to some of the posts. Sorry for that. I have changed the settings now. If some of the comments (especially these one with questions) are still up to date (some are quite old) let me know and I will try to help.

The last blog entry is a while ago, but that does not mean that nothing has happened in the meantime. Nicolas added some features and bugfixes and we are preparing a new release soon.
The people who followed the blog know that I had a hard time to p2-enable the update site. After getting this to work I concentrated on the deployment process, because one-click-one-deploy rules ;-)
Again I had a hard time automating the build process, but it I made good progress with it (using pde-build now).

Version 2.2.1 released

2010-10-26T16:42:00.001+02:00

A new version of MoreUnit is out with the following features:

Extension point enhancements
Extended method search has been improved (better performance and accuracy)
Different actions for running a single test method or the whole test case
Better support for TestNG (now runs several test cases at once)

Update after a long time

2010-09-20T21:44:00.003+02:00

It's time for another blog post after a long time.

Some of the latest news:

A new release is out for a while now
The MoreUnit team has grown (two motivated developers)

As I can not fall behind if the committers are so hard-working, I fixed a bug which seems to be a old one, at least the buggy code was old ;-)

Next small enhancement

2010-06-18T22:10:00.001+02:00

Tonight I implemented another small features which was on the wish list for a long time now.

If you create a test method moreUnit will now use the line delimiter from the actual formatter setting.

Small enhancement (creating additional test methods)

2010-06-17T22:41:00.002+02:00

Tonight I had some time to take a look at the list of feature requests of moreUnit.

Supporting move support for instance methods is not possible because eclipse does not allow participants in MoveInstanceMethodProcessor. So I left a comment in bugzilla and started to implement something different.

I have choosen a small enhancement: if you create a additional test method via the shortcut moreUnit appended the new test method at the bottom of the test case. I have changed that and moreUnit will append the additional test method directly below the test method in which the shortcut was pressed.

Version 2.0.1 released

2010-06-14T20:09:00.001+02:00

Today a new version of MoreUnit released. Because of the new feature id I created a new update site (because you need to uninstall older version to switch to the newest version). Thanks to Andreas who helped me to solve the problem with the missing property page.

Frustrattion again

2010-05-28T21:45:00.002+02:00

Today I wanted to play around with the new planned release and when installing the plugin the property page does not appear. That is a behaviour one of my teammates already had with the current release (and the prooblem disappeared at his laptop suddenly ...).

So now I am little bit frustrated because it does not seem to be a problem from the property page configuration :-(

Preparation for release of version 2.0.0

2010-05-27T21:58:00.002+02:00

After changing the feature id, I decided to give a higher version number to the new release.

Changing the feature id, will make it necessary to uninstall and reinstall the plugin, so I created a new update site for the plugin.

http://moreunit.sourceforge.net/update-site/ hosts the new release already, but the official release will take some more days (to update documentation...)

Not that a big deal

2010-05-24T12:36:00.005+02:00

While playing around with Buckminster I read about the p2.mirror-Ant task. That's excatly what I am looking for: merging a new release into a p2-enabled update site. A great pity that it took so long to find it.

I played around with it on my test update site and everthing worked fine.

Perhaps p2-frustration will come to an end...

... and for the Germans: Kaum macht man's richtig schon geht's ;-)

Next try: Buckminster

2010-05-23T20:44:00.003+02:00

While looking around to find a nice tutorial how to automate p2-update-site generation I found a link to Buckminster. In the introduction (why use Buckminster) it says:

As a developer, you want to stay focused on the construction of your code, you expect it to be built interactively giving you instant error feedback.

That is exactly what I am looking for :-)

Let's start reading the introduction and try it out...

Patch and missing jar

2010-04-13T21:18:00.002+02:00

Today a teammate had a problem with MoreUnit. He can't see property pages of MoreUnit but everything else worked fine. This evening I tried to reproduce this problem in a fresh installation but had no success. Googling around did not give any hints.

While working on this I recognized that update site does not offer the latest release 1.3.3 anymore. I'm using archive-path in the site.xml so that sourceforge tracks my downloads but the direct link to the feature jar has been moved. Really annoying. It is the second time that my update site is broken because the download links did not work anymore.

So I decided to remove archive path inn the site.xml and will upload the jars directly into to updates site directories. This will cause a loss of the download statistic, but how cares...

Move method refactoring support

2010-03-23T22:05:00.002+01:00

I got feedback that move method refactoring is not working.

Yes thats absolutely true. Although there is already a class MoveMethodPartiticipant the Change was not created. Seems that I just forgot to implement it.

This is fixed and available in HEAD.

Implementing features is much more fun than working on the update site :-)

p2 and no end

2010-03-21T21:29:00.002+01:00

Today I decided not to give up the attempt to p2-enable the update site and I found a blog post with a migration guide:

http://plosquare.blogspot.com/2009/05/migrating-eclipse-update-sites-to-p2.html

Perhaps I will get it work with this article, but why does eclipse not offer such a guide?

Again troubles with update sites

2010-02-07T21:23:00.003+01:00

Today I wanted to prepare a new release of MoreUnit. But when testing everthing with the test update site the plugin does not work because of:

Unable to access file "plugins/org.moreunit_1.4.0.jar!META-INF/MANIFEST.MF".

WTH is going on? The Manifest is in the JAR, googling around did not help very much.

It is really annoying to spend so much time about update sites. It is the first time thinking about stopping to work on this project and spending my freetime for something else.

It's working

2010-01-21T22:23:00.002+01:00

Tonight I found out what I was doing wrong. I forgot to add the new version to the catgory.xml. As a consequence my update appeared but was uncategorized. Removing the corresponding checkbox showed the update. I fixed that and now the update appears as it should.
Not that a big thing (if you know what you have to do).

Fighting with update sites

2010-01-20T22:14:00.002+01:00

Today I played around with my test update site, but with no success. It was not possible to add a new release and update to that (p2-enabled). I think it is a quite easy task for experienced eclipse plugin developers, but if you are a free-time open source developer who wants to concentrate on adding features to a plugin it is annoying to spend so much time for those things :-(

Test Updatesite p2-enabled

2010-01-18T22:23:00.003+01:00

Tonight I uploaded a test update site on http://moreunit.sourceforge.net/org.moreunit.updatetest/ which should be p2-enabled. I used the File > Export > Deployable features to generate a artifacts.xml and category.xml which should be enough to p2 enable MoreUnit (hopefully). The update site seems to work so I think it's a good start.

Patch and p2

2010-01-17T22:07:00.002+01:00

Tonight I integrated a patch to start tests from the CUT.
After that I started to read a little bit about p2 again, because MoreUnit is not p2 enabled yet. Last time I tried, it did not work properly and documenation was quite rare. Todays try was not very successfully too. Documentation about update sites on eclipse.org is outdated and the p2 site wiki did not offer a easy switch guide for plugin developers from older update sites :-(

Cleanup in the tests

2009-11-07T21:25:00.002+01:00

The tests have not been implemented very "nice". CompilationUnits got created but did not get deleted after the test run. Tonight I added cleanup code to the test methods which created java files. At first I made a mistake and tried to delete the primary type and was wondering why the java files still existed, now I call delete on the corresponding compilation unit and the tests run fine and much faster now after all of the refactorings :-)

Refactoring Tests

2009-10-28T21:50:00.002+01:00

The unit tests for MoreUnit are quite slow. But after switching to JUnit4 a while ago, I started to improve performance tonight which is quite easy because of @BeforeClass and @AfterClass.

Bugfix for enums

2009-10-19T21:45:00.002+02:00

There was a bug in MoreUnit for switching in enums. This is fixed in HEAD. When writing a test for this bug I recognized that one test does not run anymore. It causes an OutOfMemory all the time. I needed to comment out this test. At the moment I don't understand why this test causes these problems becaue I just switched the eclipse version and didn't change my code. But this problem has to wait for another evening with some freetime.

Bugfix outline view

2009-10-06T21:46:00.002+02:00

Tonight I fixed a bug in the outline view for missing test methods. Since Galileo the outline view did not synchronize with the active part anymore. The reason was that PageBookView#partHidden removed the PageRec with the MethodPage and switched to the defaultRec (no outline) and the PageRec was never switched again.
As a solution MissingMethodViewPart#partBroughtToTop now checks if the defaultRec is still shown and switches back if neccessary.

Bugfixng time

2009-09-11T22:05:00.000+02:00

Today I fixed two bugs which caused NPEs. Thanks for bug reporting!

Galileo release

2009-07-14T19:53:00.002+02:00

While Galileo is out for a while I switched just last week to the new version.
What I really bother about is the lack of extension locations (about which I blogged already about Ganyemde).
But now I gave up with it and switched to .link files to share my plugins for my different eclipse versions.
The most important thing for me in the new release happened behind the surface. I am a Mac user and after Carbon is out I already followed the milestones of Galileo in Cocoa.
It is great how fast the SWT team has ported because I think that was not quite easy.
The coolest new feature in Galileo is block editing. That rocks and was one of the missing features which urged me to open an external editor. Thanks a lot.

Switched to JUnit 4

2009-06-17T21:09:00.001+02:00

Today I switched the tests to JUnit 4 which was on my task list for a long time.

MoreUnit 1.3.1 released

2009-03-22T10:57:00.001+01:00

Some minutes ago a new version of MoreUnit was released.
What happened:

Prefix for testmethod names is now configurable.
Marker in the editor can be configured via preferences.
Bugfixing

Second test cycle finished

2009-03-18T21:38:00.002+01:00

At the moment I am preparing a new release. The first test cycle showed some bugs which are fixed now. In the second test cycle now problems occured. So moreUnit is quite close to its next release.

Homepage update prepared

2009-02-18T22:14:00.001+01:00

There are enough new features/bugfixes now to start preparing a new release. Today I have updated the homepage. Test phase of version 1.3.x can be started now.

Annotation instead of marker

2009-02-15T18:30:00.004+01:00

As moreUnit marker do show yellow marker on the right side of the editor (overview ruler) I changed the implemented and moreUnit now uses annotations which are completed configurable by the user within the preferences.

Test refactoring

2009-01-25T21:12:00.000+01:00

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

More tests

2009-01-23T22:26:00.001+01:00

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

2009-01-18T21:18:00.002+01:00

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

2009-01-15T21:00:00.003+01:00

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

2009-01-04T15:10:00.002+01:00

A new version of MoreUnit is available.

Preparing next release

2008-12-17T21:50:00.002+01:00

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

2008-12-10T22:38:00.003+01:00

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.

Started test refactoring

2008-11-30T21:44:00.001+01:00

The actual tests of moreUnit contain some code smells. Tonight I started to refactor the tests.

New feature finished

2008-11-27T22:21:00.002+01:00

A basic version to support package rename refactorings has been implemented earlier this week. Tonight I enhanced the basic version with some security checks (no rename if a package within a testfolder gets renamed).

Package rename

2008-11-24T21:35:00.001+01:00

Some weeks ago there was a bug report that a package rename doesn't cause moreUnit to rename corresponding test packages. Tonight I implemented a first version, which handles package rename. But there are still some enhancements neccessary: don't rename if refactoring is started in a test source folder...

Bugfixes

2008-11-23T22:17:00.003+01:00

Improved TestNG support seems to work now. In addition I fixed a bug which was reported from the SWTBot developer. At first I was not able reproduce the problem but as SWTBot is open source I did checkout the project and was able to see the buggy behaviour. Two bugfixes later switching seems to work again :-) Time to say goodnight.

First tests

2008-11-19T20:40:00.004+01:00

After the implementation I started to test the new wizard page but it seems to be a little buggy, the wizard doesn't recognize the test type selection. Some bug fixing is necessary.

NewTestCaseWizard with TestNG

2008-11-16T21:33:00.003+01:00

The new testcase wizard page one supports class creation for TestNG now. Just implemented and not tested yet. I think it would be good to look for an opensource project which writes TestNG tests to take a look how TestNG is used in projects, because I do use JUnit only.

Weired exceptions

2008-11-04T21:50:00.002+01:00

Tonight I wanted to work on the new wizard page for TestNG support.
After integrating a first version some weired errors occured:


04.11.08 20:25:57 [0x0-0x2a02a].org.eclipse.eclipse[216] java.lang.NoClassDefFoundError: ch/ethz/iks/slp/ServiceLocationEnumeration
04.11.08 20:25:57 [0x0-0x2a02a].org.eclipse.eclipse[216]  at java.lang.Class.getDeclaredConstructors0(Native Method)
04.11.08 20:25:57 [0x0-0x2a02a].org.eclipse.eclipse[216]  at java.lang.Class.privateGetDeclaredConstructors(Class.java:2357)
04.11.08 20:25:57 [0x0-0x2a02a].org.eclipse.eclipse[216]  at java.lang.Class.getConstructor0(Class.java:2671)
04.11.08 20:25:57 [0x0-0x2a02a].org.eclipse.eclipse[216]  at java.lang.Class.newInstance0(Class.java:321)
04.11.08 20:25:57 [0x0-0x2a02a].org.eclipse.eclipse[216]  at java.lang.Class.newInstance(Class.java:303)
04.11.08 20:25:57 [0x0-0x2a02a].org.eclipse.eclipse[216]  at org.eclipse.osgi.frame

Summary

2008-11-03T21:33:00.003+01:00

A long time is gone since my last blog. There was a new release of MoreUnit (1.1.4).
After the release I had some weeks off for a vacation. Tonight I started to improve TestNG support. Therefore I have to extend the TestCaseCreationWizard of the JUnit eclipse plugin. As a consequence I have to use code from org.eclipse.jdt.internal.* :-(

Documentation update

2008-09-01T20:56:00.002+02:00

After a long summer break I started to finish the last bugfixes (yesterday) and tonight I began to update the documentation. Because there a several new features (e.g. project specific settings with source/test-folder mapping) it would be nice to have some examples/screenshots for this.

Ganymede release

2008-07-31T21:46:00.001+02:00

This week I switched from Europe to Ganymede and here is what happened:

First of all i missed the 'Software Updates/Manage configuration' menu which I used to add my extension locations with every new release/milestone.
What happened? With Ganymede the update mechanism changed (p2). After googling I found several posts about this topic. As a hotfix I linked my extension from the dropins folder. But I dislike this hack because I think this will not work with plugin updates. As a consequence I started reading some sites about p2 and found lot's of stuff about cool new features like bundle pooling, but what I missed was an short/easy tutorial to get these stuff working for me.
Conclusion: p2 sounds interesting but will take some time to get configured if you want to use bundle pooling.

After working with Ganymede for a while I had problems with my cursor, it disappear and reappeared only if I moved the invisible cursor out of the eclipse workbench window. This is a "annoying feature" so I wanted to find out if other users have the same problem working with Ganymede on Mac.
A short search in bugzilla and the following entry occured:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=241671
Exactly the same problem, so I added a comment. In the meanwhile the bug is fixed. This really rocks about eclipse :-) A open bug database and fast feedback from the team. Cool.

A small new nice feature is the 'Restart' menu.

That's it for the first days using Ganymede.

Small bugfix for TestNG

2008-05-26T20:22:00.000+02:00

There was a bug using TestNG. In the testcase creation wizrd MoreUnit chose the wrong superclass (org.junit.TestCase). This is fixed now.

Missing validation

2008-05-15T19:35:00.001+02:00

The new property page did not validate if the user configured at least one folder as test folder for the project and threw a nasty NPE. So I have added some validation and show a error message if the test source folder config is not finished yet.

Another bugfix

2008-05-13T20:58:00.003+02:00

There was a problem with sourcefolder in a subfolder (e.g. "test/src").
So I've written some tests for this and made them pass.
Hopefully there are no more bugs because of the huge refactoring for source folder mapping support.

Bugfixing

2008-05-05T20:58:00.002+02:00

There were some bugs with the new pre-release, so I spent some time in bugfixing.
Last week I got a mail about a TestNG-problem with moreUnit.
So I'm still working on bugfixing.
As the weather is great at the moment my progress is not so good...

Preparing new release

2008-04-23T20:53:00.002+02:00

After 10 days of vacation I am back again. I fixed a bug with the project specific settings. Now it's time for a new release (1.1.x). CVS has a new tag now and test phase is started.

User settings

2008-03-23T14:41:00.002+01:00

The new property page for MoreUnit is finished. Last week I spend some time to get the test running again.
There was a enhancement request to store the settings within the project. Today I got started with scopes for preferences and implemented a first version which stores the project specific settings within the project folder.

Source folder mapping

2008-03-16T21:32:00.003+01:00

This weekend I implemented the source folder mapping. For every project you can configure test folder and corresponding source folder. It was quite a lot work to make moreUnit run again. Switching seems to work fine again. But there is still much more to do.
Additionally I got some user feedback about a preformance leak. Markus Gebhard gave very valuable feedback about some performance problems. So I invested some time to solve this problem and Markus started his profiler again => MoreUnit is a lot faster now :-)

Checkbox for project specific settings

2008-03-12T21:24:00.002+01:00

To enable/disable project specific settings I added a checkbox above the tabs. I have worked with JFace for some evenings now and it's fun to use.

Tabs for properties

2008-03-11T21:16:00.002+01:00

For a better design I started to reimplement the properties. There should be only one Property page for moreUnit. To have enough space for all the settings I'd like to split them into two tabs.
Todays challenge was to get involved with Tabs in JFace. It was quite easy after I found the classes (TabFolder and TabItem) for it.

Working prefs

2008-03-07T22:05:00.002+01:00

The converter for the prefs are integrated now and everthing seems to work fine.
There are four places, where this pref must be checked (which is not implemented yet)

label decoration
marker
jump
test code creation

Converter for prefs

2008-03-05T22:14:00.002+01:00

Tonight I've written the converter methods:
PluginTools#convertStringToSourceFolderList
PluginTools#convertSourceFolderListToString

This needs to be integrated to the preferences/properties now.

How to store complex types in prefs

2008-03-04T21:39:00.002+01:00

As the property page for the test source folder is almost completed, I'm wondering (like yesterday) how I can store complex type in the preference-store. IPreferencesStore only handles some basic types. All I found out tonight is the existence PreferencesConverter-class which allows conversion of some complex types between their string representation. But the type I need for MoreUnit is not part of the converter class :-(

Progress with new property page

2008-03-03T21:43:00.002+01:00

Tonight I proceeded with the implementation of the new property page. Everthing seems to work fine. What is still missing is the integration of the preferences. I'm wondering how I can make complex objects like IPackageFragmentRoot persistent. There are only setters for some basic types. But this is a job for another evening.

Cool new property page

2008-03-02T21:52:00.002+01:00

Last week there was some user feedback about the possibilties to configure test source folder.
This weekend during napping I had the idea how to implement this feature request.
After some hours of work I have created a new property page which shows the test source folder (as preferences are not adapted yet for the new feature this page shows all source folder of the underlying project). Additionally I started a wizard for the unit source folder selection.
I learned a lot of stuff about JFace and this was really fun :-) (I'm hoping to find some more freetime to work an this soon)

Minor refactorings

2008-02-29T22:40:00.002+01:00

While finishing the new implementation for marker updates I found some minor code smells and removed them. Additionally within these refactorings I fixed a bug for invalid marker update (which happend under some circumstances if you had multiple tests for one class).

Refactoring marker update

2008-02-23T20:00:00.002+01:00

The moreUnit now marker get updated every time you open a file.
I have added an IPartListener which starts the marker update every time an IEditorPart is opened or brought to top.

Marker for editor

2008-02-20T22:18:00.002+01:00

Yesterday I finished the test refactorings. So today I started to do some maintenance. At the moment users have to scan for marker to see them in the editor. The markers are persistent and saved when quitting the workspace.
An enhancement would be to update the marker for the open editor (and no scan for all projects in the workspace will be neccessary anymore).
To implement this I created MarkerUpdater which handles the creation of the markers of an IType. To eat my own food, I used MoreUnit to create plugin tests for MarkerUpdater :-)

Test refactoring

2008-02-18T21:33:00.002+01:00

Some weeks ago I started to read "XUnit Test Patterns - Refactoring Test Code" and found some test smells within moreUnit. So I started to refactor the testcode to improve maintainability. It's always nice to learn something new and to improve my own code.

Version 1.0.2

2008-02-17T20:52:00.003+01:00

After a long while of preparation I released version 1.0.2 of MoreUnit this weekend with some new features:

TestNG support
project specific settings
move refactoring support
improved matching for class under test
some bugfixes

It's really cool that I figured out how to address the sourceforge-release-site within my update site. From now on there will be a realistic download statistic including all update-site-users of MoreUnit.

Update project homepage

2008-02-10T21:19:00.000+01:00

Last week I redesigned the project homepage and updated the documentation for the upcoming release which is planned for next week.

Second pre-release version

2008-02-06T21:09:00.000+01:00

There had been some bugs in the first pre-release version. During bugfixing I finished the refactoring to move all the tests to org.moreunit.test.
Now there is a second pre-release version and I hope to release during the next days.

Test project for moreUnit

2008-01-29T22:07:00.000+01:00

Started to create a test project for moreUnit (org.moreunit.test) to reduce dependencies.
It took me while to figure out how it works.
Short summary:

Create a plugin-project without content
Copy plugin dependencies from MANIFEST.MF
Add org.moreunit as a plugin dependency
Needed to export the moreunit-packages ('Runtime'-tab in plugin.xml)

Preparation of a new release

2008-01-17T21:32:00.000+01:00

I am planning to release a new version of moreunit and started to test the actual version.
There are some bugs which should be fixed but half of the work seems to be done.

Preferences UI

2008-01-07T21:08:00.000+01:00

Because of the project specific prefs it was necessary to clean up the UI a little bit.
I redesigned the prefix/suffix configuration (which needs less space now).
As a consequence only one pref page is needed.

Some small enhancements

2008-01-02T21:50:00.000+01:00

Fixed a NPE-bug, if the package does not exist, when a move refactoring needs to move some tests as well.
Started to clean up the preference page.

Removed some code smells

2007-12-11T22:02:00.001+01:00

Before committing the current MoveDescriptor implementation I refactored the code a little bit.

There are still some things to do to prepare a new release:

Test MoveDescriptor with some different situation (missing packages...)
Take a more detailed look at the patch for project specific settings
There are some smaller bugfixes needed for a smooth integration of TestNG into the wizard.

Move support finished

2007-11-28T21:45:00.000+01:00

Today I finished move support.
There were some smaller enhancements that needed to be done.
But now everthing seems to work fine.
I think this will be the feature-freeze for the next upcoming moreUnit-Release.

Misery of move - SOLVED

2007-11-27T22:11:00.000+01:00

Today I solved the problem of missing imports and package declaration.
The following method call is the reason

MoveDescriptor#setMember

This method instantiates the wrong MoveProcessor (or in more detail the wrong Policy).
Using

MoveDescriptor#setResources

is the solution :-)

Misery of move

2007-11-19T22:16:00.000+01:00

Today I recognized that the move refactoring doesn't work correctly. Imports and package declarations are missing :-(
I'm wondering how long this will take to solve.
Why aren't there any examples and no documentation :-(

Magic of move

2007-11-18T22:14:00.000+01:00

Today is move refactoring day ;-)
After a long time, today I have implemented move refactoring via descriptors.
The NPE I had on Friday was a bug which is fixed in 3.4 M 3.
The last thing I have to do now is to get the correct source folder for the refactoring.

It's working!!!!

2007-11-16T22:06:00.000+01:00

After lots of disappointing hours I have made a great progress tonight.
Rename refactorings work now with descriptors.
The problem was the following line:
renameJavaElementDescriptor.setJavaElement(typeToRename.getCompilationUnit());

If I don't get the compilation unit of the type the refactoring processor does not get initialized and the checkFinalConditions crashed with a NPE.

After this I tried to implement the move refactoring.
The move seems not to work fine yet:

java.lang.NullPointerException
at org.eclipse.jdt.internal.corext.refactoring.reorg.DeleteChangeCreator.createDeleteChange(DeleteChangeCreator.java:83)
at org.eclipse.jdt.internal.corext.refactoring.reorg.ReorgPolicyFactory$MoveSubCuElementsPolicy.createChange(ReorgPolicyFactory.java:1812)
at org.eclipse.jdt.internal.corext.refactoring.reorg.JavaMoveProcessor.createChange(JavaMoveProcessor.java:158)
at org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.createChange(ProcessorBasedRefactoring.java:234)
at org.moreunit.refactoring.MoveClassParticipant.createChange(MoveClassParticipant.java:115)
at org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.createChange(ProcessorBasedRefactoring.java:250)
at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:121)
at org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:209)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1797)
at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113)

But some more time for coding and this will be solved hopefully.

MoveDescriptor continued

2007-10-28T20:50:00.000+01:00

I tried to get the move refactoring via descriptors to work.
As posted in
https://bugs.eclipse.org/bugs/show_bug.cgi?id=61817
there is bug in the current eclipse release at instantiating the move descriptor.
The workaround posted in this bug doesn't seem to work as well because the createChange implementation tries to instantiate the descriptor the "buggy" way.
As a consequence I have to try to use the latest 3.4 milestone as it is said that this bug is fixed then.

On the search journey

2007-09-28T21:53:00.000+02:00

I tried to find some examples or some documentation how to use the new refactoring API via descriptors but wasn't successful. If I try to instantiate a MoveDescriptor from a MoveContribution I get a ClassCastException. In the tests the Descriptors are instantiated directly but this is not recommended.

Still working on move refactoring

2007-09-27T21:20:00.000+02:00

Today I figured out, how my workspace code is used, when I startup a eclipse application within eclipse. The problem was a incompatibility with JDT, which I imported in my workspace. After closing all JDT related plugins in my workspace my code is used again. I'm wondering where from the launched eclipse application took the older version of my plugin although it was deactivated in my extension location?
Whatever...
At the moment I'm trying to instantiate a correct MoveDescriptor to handle class move refactorings.

Problem with extension location

2007-09-25T21:30:00.000+02:00

Tonight I wanted to progress with move refactorings but I realized a problem with the extension location. If I start a eclipse application from the run dialog the same extension location as the eclipse installtion is used. This is very bad, because I eat my own food and develop MoreUnit with MoreUnit. But now I have a conflict and the manipulated code from my workspace is not used :-(

Started move refactorings

2007-09-19T21:20:00.000+02:00

This evening I have taken a look to support move refactorings.
Within Eclipse 3.3 the API has changed and refactorings are done via descriptors.

Worked on TestNG support

2007-09-02T21:26:00.000+02:00

Today I extended NewTestCaseWizardPageOne to add TestNG support.
It was necessary to override a several methods to get it work, but I think the majority of the work is done now.

TestCaseWizard

2007-08-24T20:32:00.000+02:00

To support TestNG a extended TestCaseWizard is necessary.
As a start I extended the TestCaseWizardPageOne and overrode createJunit4Controls.
The new radio button appears but the finish button doesn't get enabled after clicking.

Integration of TestmethodCreator

2007-08-12T19:11:00.000+02:00

The integration of TestmethodCreator is finished.
The preference page is split up in two pages as well.
Now the TestNG support can be implemented which should be quite easy now.

Tests written

2007-08-11T21:16:00.000+02:00

I've written some tests for TestMethodCreator and found a small bug in my implementation.

TestMethodCreator implemented

2007-07-12T21:03:00.000+02:00

The implementation of TestMethodCreator is almost finished. Some more tests are needed and then I can integrate it into the plugin.

Implementation of TestmethodCreator

2007-07-10T22:15:00.000+02:00

Today I worked on the implementation of TestmethodCreator (TestNG)-support, but I'm not quite sure about the design of this class (encapsulation of preferences like JUnit3/4 as well?).

Started TestNG support

2007-06-28T21:13:00.000+02:00

Yesterday I started the TestNG support.
I decided to implement a creator-class which encapsulates the creation of testmethods.
As there are several different types of test (JUnit 3.8, JUnit 4, TestNG, additional tests for exisiting testmethods), I think this is a good idea.

Fixed broken tests

2007-06-15T21:42:00.000+02:00

After switching back to JUnit 3.8 I realized that the tests were broken.
There was a bug in SelectedJavaProjectProvider which broke the tests.
But now everything works fine again :)

Switching back to JUnit 3.8

2007-06-14T21:30:00.000+02:00

I was not able to figure out what the reason is.
If I switch back to JUnit 3.8 everything works fine.
So this seems to be my choice because after searching for a while it seems that there are many other people having the same problem (without solution).

No runnable methods

2007-05-11T23:00:00.000+02:00

For yesterdays bug I wanted to write a test, but I recognized that the plugin tests don't run anymore: Exception, no runnable methods.
At the moment I can not see the reason for this problem.
Googling for this message said that missing annotations cause this exception, but adding the required annotation didn't help :(

Bug when switching back

2007-05-09T20:44:00.000+02:00

Today I got some feedback that switching back from the test is not working.
If you have two classes Example.java and ExamplePlusExtension.java and a test ExamplePlusExtensionTest.java and although flexible test case naming is not activated moreUnit switches to Example.java.
There are two reasons for this bad behaviour:
1. TestCaseTypeFacade#getCorrespondingClassUnderTest doesn't use the pref and uses flexible testcase naming pre default
2. If MoreUnit finds more than one possible class under test it just switches to the first one and doesn't ask the user to make a choice.

That's bad :(

Shame on me

2007-05-07T21:56:00.000+02:00

Thanks to Benny who opened my eyes. Code generation with a protected constructor was the reason for the error. But now I was able to add a detail pref page for TestNG activation.
When Benny wrote the mail with the solution for my stupid mistake I planned not to code after work again. Today I broke my rule, but I have choosen a glas of red vine as my pair programmer and it seems to be a good choice :)

Still no second pref page

2007-05-04T22:18:00.000+02:00

I don't what the problem is with this sh** second pref page.
But I made a bugfix (NPE in isJavaFile).
So at least I did something useful tonight :)

Splitting preferences

2007-04-16T22:15:00.000+02:00

Today I wanted to start to add support for TestNG.
Therefore I added a new preference page (to get a detail pref page for the additional settings).
It's a pity that I didn't figure out yet why I am getting a "error while creating preference page"-message when opening the preferences all the time :(