Kommentare zu: Unit testing annotation based Spring MVC controllers

Von: Jörg

Jörg — Mon, 21 Sep 2009 10:33:43 +0000

Don’t worry. Learned about the class extension. A classic RTFM case …

Von: Jörg

Jörg — Mon, 21 Sep 2009 10:17:40 +0000

I just tried your code and I’m getting
java.lang.IllegalArgumentException: pkg.MyController is not an interface
at java.lang.reflect.Proxy.getProxyClass(Proxy.java:362)
197)

error as MyController isn’t an interfacce. But yours isn’t either. Do you have any idea why that might be? I’m using Junit 4 and the latest EasyMock (2.5.2)

Jörg

Von: Mediocre-Ninja.blogSpot.com

Mediocre-Ninja.blogSpot.com — Sat, 01 Aug 2009 03:13:29 +0000

I think using EasyMock and EasyMockUnitils is easier for testing @MVC controller .

I have no idea why pure mapping URL testing is neccessary, though.

Von: Christopher

Christopher — Wed, 27 May 2009 14:50:03 +0000

Hi!
I saw, that you helped somebody to create Hibernate test with AbstractTransactionalHibernateTest JUnit class

Where can I get this JUnit import? Is there a documentation about this JUnit?

Gruß Christopher

Von: david

david — Sun, 17 May 2009 08:21:05 +0000

I had the same experience going back from Restlet 1.2 to 1.1, where 1.2 uses annotations and thus you can easily test the “plain” @Get, @Post etc methods. Restlet 1.1 uses inheritance, which makes it much harder to test. That’s really an advantage of annotations.