Have you looked at selenium? Your not really "unit" testing here.

On Sat, May 9, 2009 at 7:41 AM, Marko Sibakov <marko.siba...@ri.fi> wrote:

> Like Martijn said i also strongly recommend to take a look at the
> jdave-wicket's selectors (http://www.jdave.org/).
>
> examples =>
> http://svn.laughingpanda.org/svn/jdave/trunk/jdave-wicket/src/test/jdave/wicket/PageWithItemsSpec.java
>
>
> with form tester it goes like this =>
>
>           form = wicket.newFormTester(selectFirst(Form.class,
> "form").from(panel).getPageRelativePath());
>           form.setValue("name", "wicket");
>           form.setValue("address", "jdave");
>           form.submit();
>
> MSi
>
> Martijn Dashorst wrote:
>
>> See jdave-wicket for better test support. Slated to come to you in Wicket
>> 1.5
>>
>> Martijn
>>
>> On Fri, May 8, 2009 at 5:48 PM, Martin Makundi
>> <martin.maku...@koodaripalvelut.com> wrote:
>>
>>
>>> Hi!
>>>
>>> I use TDD: I spend 60% of my time type-checking and path-checking my
>>> wicketTests and components.
>>>
>>> I always have the wrong path and I must prinDocument and iterate to
>>> get it right....
>>>
>>> Anybody have the same experience?
>>>
>>> How about introducing type-safety and path-safety/identity into
>>> component hierarchies?
>>>
>>> Can this be done?
>>>
>>> **
>>> Martin
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>>> For additional commands, e-mail: users-h...@wicket.apache.org
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>

Reply via email to