classes for unit 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-tester Contains common classes for unit testing (like WicketTester). wicket-core wicket-core-tests Contains test cases for wicket- core. wicket-core, wicket-tester wicket-request This module contains approach we must manually put 16 them inside every page. If we were using JSP we would probably end up using include directive to add layout areas in our pages. We would have one include for each of

classes for unit 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. approach we must manually put 15 them inside every page. If we were using JSP we would probably end up using include directive to add layout areas in our pages. We would have one include for each of layout area we will build a panel like the one above that holds the appropriate HTML markup. In the end we will have the following set of panels: • HeaderPanel • FooterPanel • MenuPanel Content area

classes for unit 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. approach we must manually put 15 them inside every page. If we were using JSP we would probably end up using include directive to add layout areas in our pages. We would have one include for each of layout area we will build a panel like the one above that holds the appropriate HTML markup. In the end we will have the following set of panels: • HeaderPanel • FooterPanel • MenuPanel Content area

classes for unit 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. approach we must manually put 16 them inside every page. If we were using JSP we would probably end up using include directive to add layout areas in our pages. We would have one include for each of layout area we will build a panel like the one above that holds the appropriate HTML markup. In the end we will have the following set of panels: • HeaderPanel 21 • FooterPanel • MenuPanel Content area

● With “just JUnit” we mean: 1) We don’t need to have a running server 2) We don’t need to run tests for a specifc browser (like we do with Karma) 3) No additional library required, just Wicket and