Started TestNG support

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

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

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

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

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

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

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 :)