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
