Hi! I often find myself spending a tremendeous amount of time mind-boggling with Component:paths for my WicketTester tests.
I assume that it would be pretty easy to code a 'WicketTest recorder'. The solution would probably be some kind of filter properly attached into the wicket framework at runtime, and it would produce assertComponent() and assertRenderedPage() statements for all of the clicked elements in the desired clicking order. This could significantly simplify making UI tests for lengthly sequences and processes... Has anybody tried this before? Any pointers? ** Martin --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
