Thanks Tom for the suggestions. I didn't know these things.
On Fri, Aug 17, 2012 at 12:14 PM, Tom Norton <
tomwnorton.mailing.li...@gmail.com> wrote:
> My unit tests construct the WicketTester in the setUp method. I also
> extend WicketTester so that I can mock our database-driven content system
My unit tests construct the WicketTester in the setUp method. I also
extend WicketTester so that I can mock our database-driven content
system and Spring Application Context (wicket provides a mock for this:
http://wicket.apache.org/apidocs/1.5/org/apache/wicket/spring/test/ApplicationContextMo
Any suggestions regarding this? Thank you.
On Thu, Aug 16, 2012 at 10:04 AM, James Eliyezar wrote:
> Friends,
>
> Just curious to find out what best practices do you all follow when using
> WicketTester.
>
> FYI, to improve the performance of unit tests, we decided to use a shared
> instance of W
Friends,
Just curious to find out what best practices do you all follow when using
WicketTester.
FYI, to improve the performance of unit tests, we decided to use a shared
instance of WicketTester across our unit tests.
The tests worked fine in Wicket 1.4.x but fail after upgrading to 1.5.x
when r
