default after onClick has been executed, Wicket will send back to the current page to the client web browser. If we want to navigate to another page we must use method setResponsePage of class Component: @Override public void onClick() { //we redirect browser to another page. setResponsePage(AnotherPage.class); } input a page instance instead of a page class: @Override public void onClick() { //we redirect browser to another page. AnotherPage anotherPage = new AnotherPage(); setResponsePage(anotherPage);

default after onClick has been executed, Wicket will send back to the current page to the client web browser. If we want to navigate to another page we must use method setResponsePage of class Component: @Override 12 public void onClick() { //we redirect browser to another page. setResponsePage(AnotherPage.class); } input a page instance instead of a page class: @Override public void onClick() { //we redirect browser to another page. AnotherPage anotherPage = new AnotherPage(); setResponsePage(anotherPage);

default after onClick has been executed, Wicket will send back to the current page to the client web browser. If we want to navigate to another page we must use method setResponsePage of class Component: @Override public void onClick() { //we redirect browser to another page. setResponsePage(AnotherPage.class); } input a page instance instead of a page class: @Override public void onClick() { //we redirect browser to another page. AnotherPage anotherPage = new AnotherPage(); setResponsePage(anotherPage);

default after onClick has been executed, Wicket will send back to the current page to the client web browser. If we want to navigate to another page we must use method setResponsePage of class Component: @Override public void onClick() { //we redirect browser to another page. setResponsePage(AnotherPage.class); } input a page instance instead of a page class: @Override public void onClick() { //we redirect browser to another page. AnotherPage anotherPage = new AnotherPage(); setResponsePage(anotherPage);

default after onClick has been executed, Wicket will send back to the current page to the client web browser. If we want to navigate to another page we must use method setResponsePage of class Component: @Override public void onClick() { //we redirect browser to another page. setResponsePage(AnotherPage.class); } 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 JUnit (no need of browser automation tools like Selenium) Test in isolation