[WICKET-1434] WicketTester.startPage(Class) does not trigger WebRequestCycle.onBeginRequest

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.3.2
• Fix Version/s: 1.3.3
• Component/s: wicket
• Assignee: Igor Vaynberg
• Reporter: Lars Vonk
• Created: 18/Mar/08 22:14
• Updated: 23/Mar/08 02:49
• Resolved: 23/Mar/08 02:49

Description

While using WicketTester to test my WebApplication that is using a custom WebRequestCycle and WebRequestCycleProcessor I noticed that WicketTester does not follow the same RequestCycle as it would do when running in a real live environment resulting in MyWebRequestCycle.onBeginRequest not being called.

Using startPage(Page) will call MyWebRequestCycle.onBeginRequest but then the IRequestTarget that is resolved from the Request indicates the Request comes from the DummyHomePage.testPage link.

Can startPage be implemented that it really resembles the real live environment? After some research and testing I came up with this implementation, maybe it can be used:

public Page startPage(Class pageClass) {
WebRequestCycle requestCycle = super.setupRequestAndResponse();
requestCycle.getRequest().getRequestParameters().setBookmarkablePageClass(pageClass.getName());
super.processRequestCycle(requestCycle);
return super.getLastRenderedPage();
}

Issue Links

• relates to: WICKET-1435 WicketTester.clickLink(String) only triggers the WebRequestCycle.onEndRequest