WicketTester tester=new WicketTester();
tester.startPage(new MyPage());
=== page is rendered ====
tester.getLastRenderedPage().clickLink("blah");
=== link is pressed - handler and response page processed ===
tester.getLastRenderedPage().clickLink("blah2");
=== link is pressed - handler and response page processed ===
i think as far as the pages/components are concerned there is no difference from the user clicking links in the browser.
i havent looked deeply into the code but i think this is the case. have you looked at it recently?
-Igor
On 12/18/05, Ralf Ebert <[EMAIL PROTECTED]> wrote:
Hi,
> did you check WicketTester, i think it allows you to do exactly this.
I checked this, but if I got it right it makes the changes to the
components before/after the complete response/request cycle has been
handled. It just changes the component tree after the page has been
rendered which is kind of not really suitable for good testing I
think.
Ralf
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&opclick
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
