Hi,
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
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
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 Wicke
