You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Martin Makundi <ma...@koodaripalvelut.com> on 2008/12/15 00:41:19 UTC

Recording component paths for WicketTester

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-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: Recording component paths for WicketTester

Posted by Martin Makundi <ma...@koodaripalvelut.com>.
Tnx, luckily I am using 1.4-rc1.

2008/12/15 James Carman <jc...@carmanconsulting.com>:
> 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
> <ma...@koodaripalvelut.com> 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: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: Recording component paths for WicketTester

Posted by James Carman <jc...@carmanconsulting.com>.
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
<ma...@koodaripalvelut.com> 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: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org