. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265 23. Test Driven Development with Wicket. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278 24. Test Driven Development with Wicket and Spring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 24.2. Configuration of the JUnit based integration test environment . . . . . . . . . . . . . . . . . . . . . . . . . 283 24.3. Summary . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 23. Test Driven Development with Wicket. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267 24. Test Driven Development with Wicket and Spring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268 24.2. Configuration of the JUnit based integration test environment . . . . . . . . . . . . . . . . . . . . . . . . . 270 24.3. Summary . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265 23. Test Driven Development with Wicket. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277 24. Test Driven Development with Wicket and Spring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 24.2. Configuration of the JUnit based integration test environment . . . . . . . . . . . . . . . . . . . . . . . . . 282 24.3. Summary . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 23. Test Driven Development with Wicket. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266 24. Test Driven Development with Wicket and Spring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267 24.2. Configuration of the JUnit based integration test environment . . . . . . . . . . . . . . . . . . . . . . . . . 269 24.3. Summary . . . . . . . .

Label("loginStatus")); } public final void onSubmit() { if(username.equals("test") && password.equals("test")) loginStatus = "Congratulations!"; else loginStatus Wicket Test in isolation ● Test Driven Development (and unit testing) has become a fundamental activity in our everyday-job. Wicket ofers a rich set of helper classes that allows us to test our applications additional library required, just Wicket and JUnit (no need of browser automation tools like Selenium) Test in isolation public class TestHomePage { private WicketTester tester; @Before public