On Tue, Oct 23, 2012 at 10:59 AM, James Selvakumar <ja...@mcruncher.com> wrote: > Sorry if this is asked previously. Is it advisable to use a shared wicket > tester across multiple unit tests? >
I would not recommend that. WicketTester keeps a reference to YourApplication which may keep references to any services for your app. By keeping reusing the same WicketTester you should make sure that all your services are reusable, i.e. do not keep state. > On Tue, Oct 23, 2012 at 3:39 PM, Martin Grigorov <mgrigo...@apache.org>wrote: > >> On Tue, Oct 23, 2012 at 10:38 AM, James mCruncher <ja...@mcruncher.com> >> wrote: >> > Should that call be made on "tearDown" or "tearDownClass"? >> >> It depends where WicketTester is initialized. >> >> > >> > On Mon, Oct 22, 2012 at 6:01 PM, Martin Grigorov <mgrigo...@apache.org >> >wrote: >> > >> >> Call it and try again. >> >> >> >> On Mon, Oct 22, 2012 at 11:45 AM, Arunachalam Sibisakkaravarthi >> >> <arunacha...@mcruncher.com> wrote: >> >> > No, We don't call wicketTester.destroy() at the end of tests. >> >> > >> >> > On Mon, Oct 22, 2012 at 5:01 PM, Martin Grigorov < >> mgrigo...@apache.org >> >> >wrote: >> >> > >> >> >> Hi, >> >> >> >> >> >> Do you call wicketTester.destroy() at the end of your tests ? >> >> >> >> >> >> On Mon, Oct 22, 2012 at 9:10 AM, Arunachalam Sibisakkaravarthi >> >> >> <arunacha...@mcruncher.com> wrote: >> >> >> > Hai, >> >> >> > >> >> >> > Here we are using wicket 1.5.7. >> >> >> > >> >> >> > We have a simple test for each wicket page to assert rendering like >> >> this: >> >> >> > >> >> >> > WicketTester.assertRenderedPage(Page.class); >> >> >> > >> >> >> > In our module we have 52 tests w.r.t wicket pages. >> >> >> > >> >> >> > It takes so long to run these tests. >> >> >> > >> >> >> > Please give suggestion to improve test cases that how to reduce the >> >> time >> >> >> > taken by this module. >> >> >> > >> >> >> > -- >> >> >> > *Thanks And Regards >> >> >> > Sibi.Arunachalam >> >> >> > mCruncher* >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> >> Martin Grigorov >> >> >> jWeekend >> >> >> Training, Consulting, Development >> >> >> http://jWeekend.com >> >> >> >> >> >> --------------------------------------------------------------------- >> >> >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> >> >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> >> >> >> >> >> >> > >> >> > >> >> > -- >> >> > *Thanks And Regards >> >> > Sibi.Arunachalam >> >> > mCruncher* >> >> >> >> >> >> >> >> -- >> >> Martin Grigorov >> >> jWeekend >> >> Training, Consulting, Development >> >> http://jWeekend.com >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> >> >> >> > >> > >> > -- >> > Thanks & regards >> > James Selvakumar >> >> >> >> -- >> Martin Grigorov >> jWeekend >> Training, Consulting, Development >> http://jWeekend.com >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > > > -- > Thanks & regards > James Selvakumar -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
