Hi, You could use
1- ApplicationContextMock as your spring context class 2- Mockito to create mocks of your spring beans this ways your tests will run a lot faster and they will be independent of actual backed implementation (as far as mocks behaves in exactly the same way as expected from real backend) On Mon, Feb 12, 2018 at 4: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 > -- Regards - Ernesto Reinaldo Barreiro
