Tnx, luckily I am using 1.4-rc1.

2008/12/15 James Carman <[email protected]>:
> What version of Wicket are you running?  There was a JIRA request to
> spit out the component paths in development mode:
>
> https://issues.apache.org/jira/browse/WICKET-1830
>
> Apparently it was fixed in 1.3.5 and 1.4-rc1.
>
>
> On Sun, Dec 14, 2008 at 6:41 PM, Martin Makundi
> <[email protected]> wrote:
>> 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: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to