[Webtest] [dev] Locators

[Dierk Koenig]

I fully agree.

Actually, I thought about the very same issue and 
didn't submit a selftest because I wasn't sure about the
solution.
For the naming of the step I would like to express that
it is not a self-sufficient "set" but changes the 
scope of the trailing steps. How about "withForm ..."?

There is one remaining issue (admittedly conceived):
multiple buttons in same form with same properties
(name,value) but different onclick-handlers.
This is where we would need the button index.

cheers
Mittie

> -----Original Message-----
> From: webtest-admin@lists.canoo.com
> [mailto:webtest-admin@lists.canoo.com]On Behalf Of Marc Guillemot
> Sent: Montag, 22. November 2004 9:58
> To: webtest@lists.canoo.com
> Subject: [Webtest] [dev] Locators
> 
> 
> Hi Mittie,
> 
> I've seen your commit "show need for locators" preparing for 
> re-introduction of locators. I (now ;-)) agree with the 
> need of the <index> locator for a button but I propose an other 
> solution instead of the form locator. The old form 
> locator only allowed to locate a form when clicking on a button. 
> This was fully ok as there was no need to have the form 
> "located" before as the set inputs were buffered. This isn't the 
> case anymore because actions are performed directly on 
> the form. This introduce the need for a "locateform" (or 
> "selectcurrentform") step that can be used before a <setXXXX> 
> or before a <clickbutton> making the nested form locator useless. 
> Is this ok for you?
> 
> Marc.
> _______________________________________________
> WebTest mailing list
> WebTest@lists.canoo.com
> http://lists.canoo.com/mailman/listinfo/webtest
>