. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 24.2. Configuration of the JUnit based integration test environment . . . . . . . . . . . . . . . . . . . . . . . . . 282 24.3. Summary Testing web applications is much easier: since pages and components are pure objects, you can use JUnit to test their behavior and to ensure that they render as expected. Wicket has a set of utility classes testing that simulate user interaction with web pages, hence we can write acceptance tests using just JUnit without any other test framework (unit testing is covered in chapter 23). 3.4. Wicket vs the other

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 24.2. Configuration of the JUnit based integration test environment . . . . . . . . . . . . . . . . . . . . . . . . . 283 24.3. Summary Testing web applications is much easier: since pages and components are pure objects, you can use JUnit to test their behavior and to ensure that they render as expected. Wicket has a set of utility classes testing that simulate user interaction with web pages, hence we can write acceptance tests using just JUnit without any other test framework (unit testing is covered in chapter 23). 3.4. Wicket vs the other

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268 24.2. Configuration of the JUnit based integration test environment . . . . . . . . . . . . . . . . . . . . . . . . . 270 24.3. Summary Testing web applications is much easier: since pages and components are pure objects, you can use JUnit to test their behavior and to ensure that they render as expected. Wicket has a set of utility classes testing that simulate user interaction with web pages, hence we can write acceptance tests using just JUnit without any other test framework (unit testing is covered in chapter 23). 3.4. Wicket vs the other

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267 24.2. Configuration of the JUnit based integration test environment . . . . . . . . . . . . . . . . . . . . . . . . . 269 24.3. Summary Testing web applications is much easier: since pages and components are pure objects, you can use JUnit to test their behavior and to ensure that they render as expected. Wicket has a set of utility classes testing that simulate user interaction with web pages, hence we can write acceptance tests using just JUnit without any other test framework (unit testing is covered in chapter 23). 3.4. Wicket vs the other

set of helper classes that allows us to test our applications in isolation using just JUnit. ● With “just JUnit” we mean: 1) We don’t need to have a running server 2) We don’t need to run tests for for a specifc browser (like we do with Karma) 3) No additional library required, just Wicket and JUnit (no need of browser automation tools like Selenium) Test in isolation public class TestHomePage t, "class", "myClass", false); assertEquals(2, tagTesterList.size()); Response content: JUnit code: Testing the response ● AJAX components can be tested as well “triggering” the JavaScript