xpath is also very unreadable.
 
As a side note, one of my clients has recognized the value of good html. When something is missing an id , we add an hour, per build, per testcase for manual testing of the application. It something that is now easy for the developers and project managers to see the value, of automation, and writing html that is easily testable
 
Paul
----- Original Message -----
Sent: Tuesday, June 06, 2006 9:56 PM
Subject: Re: [Wtr-general] Proposal for supporting multiple attributes

On 6/6/06, Angrez Singh <[EMAIL PROTECTED]> wrote:
Can't XPath functionality be used to access elements using multiple attributes? This is already there.

>  ie.div(:class => "MenuItem", :text => "Pulverize").click

This translates to:
ie.div(:xpath, "//[EMAIL PROTECTED] = 'MenuItem' and @text = 'Pulverize']).click

I think XPath provides much more powerful way to select element in addition to selecting it using multiple attributes. Comments?

I've run into this bug when i've tried to use xpath as you describe.

http://jira.openqa.org/browse/WTR-19
http://www.germane-software.com/projects/rexml/ticket/61

And i don't think i can wait for the REXML fix. There is also the issue of speed, which i think would make this valuable even after REXML was working correctly.

Bret


_______________________________________________
Wtr-general mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/wtr-general
_______________________________________________
Wtr-general mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/wtr-general

Reply via email to