Description
Memory requirement for running the test suite for a Wicket application increase as the number of constructed Applications (for example BaseWicketTester.DummyWebApplication) goes up.
The static applicationToClassesToGetAndSetters Map holds Applications as keys. There is no equals/hashCode so a reference for each newly constructed test Application will be stuffed in there and not reused for identical Applications.
I solved the problem for my project by implementing equals & hashCode in our DummyProjectXApplication.
There seems to be something related going on in WICKET-625 with Application.internalDestroy, which removes the Application reference when the webapp is unloaded. After a test is done with the Application it might use the same mechanism for "unloading" the application?