. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 21.4. Testing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 23.2. Testing Wicket forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263 23.3. Testing markup with TagTester stored inside the HttpSession and we can start managing them in a natural and transparent way. • Testing web applications is much easier: since pages and components are pure objects, you can use JUnit

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 21.4. Testing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266 23.2. Testing Wicket forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273 23.3. Testing markup with TagTester stored inside the HttpSession and we can start managing them in a natural and transparent way. • Testing web applications is much easier: since pages and components are pure objects, you can use JUnit

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 21.4. Testing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267 23.2. Testing Wicket forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274 23.3. Testing markup with TagTester stored inside the HttpSession and we can start managing them in a natural and transparent way. • Testing web applications is much easier: since pages and components are pure objects, you can use JUnit

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 21.4. Testing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 23.2. Testing Wicket forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262 23.3. Testing markup with TagTester stored inside the HttpSession and we can start managing them in a natural and transparent way. • Testing web applications is much easier: since pages and components are pure objects, you can use JUnit

AjaxEventBehavior.onEvent("click", target -> target.add(component)); Testing with Wicket Test in isolation ● Test Driven Development (and unit testing) has become a fundamental activity in our everyday-job. Wicket class in a Wicket testing is org.apache.wicket.util.tester.WicketTester. This utility class provides a set of methods to render a component, click links, check page content, etc... Testing the response ● WicketTester allows us to access to the last response generated during testing with method getLastResponse. Utility class Mock- HttpServletResponse is returned to extract informations from mocked