I looked into the patch and have a couple of questions. To me MockWebApplication has a clearly defined focus, together with MockXXX it provides a test environment which doesn't require a servlet container. IMO it's only problem is that it derives from WebApplication instead of delegating to a user provided application object. The problem being if you created your own Application you have to copy the code into your MyMockApplication as well (proliferation of Apps classes), which is aweful.
WicketTester/FormTesters focus is different. It is meant to provide all the assertXXX and helpers and little utils required to efficently test wicket apps. In that sense MockApplication provides the infrastructure required. And I don't yet understand why to merge both into one hugh (>1000 loc) file. FormTester hasn't changed much except that it now references WebApplicationTester instead of WicketTester. I agree that WicketTester has grown without much control and needs some refactoring as well as changes due to lessons learned. And the new tools like TagTester etc Juergen ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Wicket-develop mailing list Wicket-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-develop
