Probably you're initializing your application for each test, so you should look into speeding that up or eliminating it all together (just once for the whole suite)
Martijn On Mon, Feb 12, 2018 at 5:05 AM, James Selvakumar <ja...@mcruncher.com> wrote: > Hi, > > We have a Wicket 7.x application which uses a Spring/Hibernate backend. We > have few hundred simple Wicket tests that basically tests whether the page > has been loaded properly. Since almost all our Wicket pages use Spring > beans, we have to initialize the Spring application context for our Wicket > tests to run. And as a result our tests are extremely slow that we have > stopped running them in our main pipeline. > > What strategy do you all follow to run Wicket tests that can run fast? > > Thanks in advance, > James > mCruncher -- Become a Wicket expert, learn from the best: http://wicketinaction.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
