Any suggestions regarding this? Thank you. On Thu, Aug 16, 2012 at 10:04 AM, James Eliyezar <[email protected]>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 WicketTester across our unit tests. > The tests worked fine in Wicket 1.4.x but fail after upgrading to 1.5.x > when run using Maven. > However, Wicket 1.5 based tests pass when the tests are run using maven > fork mode "always". > > Is it advisable to use a shared instance of WicketTester across multiple > unit test classes? > Or should WicketTester should be instantiated and destroyed in the "setUp" > and "tearDown" methods in every unit test class? > > -- > Thanks & regards > James Selvakumar > mcruncher.com > > -- Thanks & regards James Selvakumar mcruncher.com
