To be honest, there's nothing wicket-specific about it. Testing AJAX is pretty easy, just use waitFor* assertions to delay until the AJAX component is loaded.
One slight irritation is that Wicket munges the id of its components, making element identification a bit tedious, so I eventually wrote a custom element locator. Best thing is to just get in and install it, try it, take over one of the provided stubs and modify it to drive your own application. It won't take you long to get into the groove. The documentation is pretty good too. Cheers, Günther Newgro wrote: > > > stiq looks very promising. Can you please provide some small snippets > howto use it in correlation with wicket? > > -- View this message in context: http://www.nabble.com/System-test-for-a-Wicket-based-web-application.-Do-you-do-it--How--tp23513449p23539242.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
