As Ernesto said your tests are slow because of Spring/Hibernate, not
because of Wicket.
You can either use mocks instead of real Spring beans or you can create the
Spring context once and reuse it for all/most tests.

Martin Grigorov
Wicket Training and Consulting
Looking for a remote position with Wicket ? Contact me!

On Mon, Feb 12, 2018 at 5:05 AM, James Selvakumar <ja...@mcruncher.com>

> 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

Reply via email to