Hi Paul,
It seems the MockEditingContext was not initialized as a rule. I have seen this
kind of behavior every time I forget the @Rule annotation.
That's not the case though. The only reason I can see to ignore the @Rule
annotation is an older version of the JUnit runner being used. Could you try to
print the JUnit version for your test?
System.out.println("JUnit version is: " + junit.runner.Version.id());
If the JUnit version is 4.7 or higher, we will have to debug more carefully.
Anyway, that is pretty weird.
Sent from my iPhone
On 18/06/2011, at 21:46, Paul Hoadley <[email protected]> wrote:
> Hi Henrique,
>
> On 19/06/2011, at 3:58 AM, Henrique Prange wrote:
>
>> You didn't misread. It's supposed to work. :)
>>
>> Could you try to run the same test using this WOUnit package [1] and send me
>> the produced log? This package adds some log messages that can help solving
>> the problem.
>
> Now I'm even more suspicious that I'm doing something wrong: I don't get any
> additional log output. (I assume it's configured to go to the console? All
> I get in the Eclipse console is some Wonder initialisation and my own
> System.out.println statement.) wounit-1.1-debug.jar is the only JAR in
> Libraries, it's on the project's build path, and I see it in the classpath
> for the run configuration with which I'm launching this test (Run As... JUnit
> Test). The project is a framework project.
>
>
> --
> Paul.
>
> http://logicsquad.net/
>
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
