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 > and Spring Application Context (wicket provides a mock for this: > http://wicket.apache.org/**apidocs/1.5/org/apache/wicket/**spring/test/** > ApplicationContextMock.html<http://wicket.apache.org/apidocs/1.5/org/apache/wicket/spring/test/ApplicationContextMock.html>). > This page talks about extending WicketTester: https://cwiki.apache.org/** > WICKET/testing-pages.html<https://cwiki.apache.org/WICKET/testing-pages.html> > > Tom > > > On Thu 16 Aug 2012 09:14:22 PM EDT, James Eliyezar wrote: > >> Any suggestions regarding this? Thank you. >> >> On Thu, Aug 16, 2012 at 10:04 AM, James Eliyezar <ja...@mcruncher.com >> >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 >>> >>> >>> >> >> > > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > users-unsubscribe@wicket.**apache.org<users-unsubscr...@wicket.apache.org> > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Thanks & regards James Selvakumar mcruncher.com
