Comments for WatirMelon http://watirmelon.com A 93% Watir Based Blog by Alister Scott Wed, 22 Feb 2012 14:36:39 +0000 hourly 1 http://wordpress.com/ Comment on Visualising software quality: using ink by Phil Kirkham http://watirmelon.com/2012/02/22/visualising-software-quality-using-ink/#comment-3773 Wed, 22 Feb 2012 14:36:39 +0000 http://watirmelon.com/?p=1216#comment-3773 Simple – but effective ! You might be onto something with this idea

]]> Comment on Death to xpath (and css) selectors in automated tests by Alister Scott http://watirmelon.com/2011/08/09/death-to-xpath-and-css-selectors-in-automated-tests/#comment-3769 Tue, 21 Feb 2012 23:45:56 +0000 http://watirmelon.com/?p=1043#comment-3769 Depends whether you care that they’re in the div or not.

]]> Comment on Death to xpath (and css) selectors in automated tests by Jonathan Cole http://watirmelon.com/2011/08/09/death-to-xpath-and-css-selectors-in-automated-tests/#comment-3768 Mon, 20 Feb 2012 23:36:21 +0000 http://watirmelon.com/?p=1043#comment-3768 Stick with XPath when you need to travel up the DOM. If you are concerned with speed, make sure you include this step after starting selenium:

selenium.useXpathLibrary(“javascript-xpath”);

]]> Comment on Death to xpath (and css) selectors in automated tests by chuckvdl http://watirmelon.com/2011/08/09/death-to-xpath-and-css-selectors-in-automated-tests/#comment-3765 Sun, 19 Feb 2012 07:39:10 +0000 http://watirmelon.com/?p=1043#comment-3765 This sort of change would require updating scripts in any case where that div was part of the ‘path’ used to identify objects. It’s more often the case the way I’ve seen xpath most often used, but it would also happen if you are defining a more explicit path using watir-webdriver.

Using a abstraction layer pattern such as Page Objects can simplify this a lot by creating a central place where you identify objects and give them a more friendly name that is then used elsewhere in your scripts. Then you have one place to make such changes when devs rename things, which makes updating scripts a lot easier.

]]> Comment on Death to xpath (and css) selectors in automated tests by Olya http://watirmelon.com/2011/08/09/death-to-xpath-and-css-selectors-in-automated-tests/#comment-3763 Fri, 17 Feb 2012 14:36:06 +0000 http://watirmelon.com/?p=1043#comment-3763 Hello!
Please give me advice, I’m a beginner in Selenium WebDriver and I used Selenium IDE before. And I have a lot of XPath selectors in my tests, but I have no idea of how to change some of them not using XPath, for example I have a table with checkboxes in the first column and IDs in the 3rd column and I need to click a checkbox in a row with ‘required_ID’ in the 3rd cell and this is how I do this with XPath:

//tbody[2]/tr[td[3]/a=’required_ID’]/td/center/input

How should I make this condition without XPath, just give me a hint. Thanks.

]]> Comment on Death to xpath (and css) selectors in automated tests by Alister Scott http://watirmelon.com/2011/08/09/death-to-xpath-and-css-selectors-in-automated-tests/#comment-3762 Fri, 17 Feb 2012 05:13:24 +0000 http://watirmelon.com/?p=1043#comment-3762 I posted a response at Stack Overflow: http://stackoverflow.com/questions/9319833/recursively-loop-through-frames-to-find-an-element-in-watir-webdriver-works-in

]]> Comment on Death to xpath (and css) selectors in automated tests by Ryan C. http://watirmelon.com/2011/08/09/death-to-xpath-and-css-selectors-in-automated-tests/#comment-3761 Thu, 16 Feb 2012 23:42:30 +0000 http://watirmelon.com/?p=1043#comment-3761 Alister,

Thanks for this post – it really adds clarity as to why a person would select Watir-WebDriver over Ruby’s Selenium WebDriver.

I’m running into a problem, which I’ve posted here at StackOverflow:
http://stackoverflow.com/questions/9319833/recursively-loop-through-frames-to-find-an-element-in-watir-webdriver-works-in

It seems like it’s kind of in the same ‘vein’ as some of the issues you highlighted here, albeit loosely. Do you have any insights?

]]> Comment on Death to xpath (and css) selectors in automated tests by mingzhu (@mingzhu) http://watirmelon.com/2011/08/09/death-to-xpath-and-css-selectors-in-automated-tests/#comment-3759 Thu, 16 Feb 2012 01:47:10 +0000 http://watirmelon.com/?p=1043#comment-3759 Imagine we have
a div tag with id=”user-nav”, which contains
a lot of inputs and links and text under the div.

]]> Comment on Death to xpath (and css) selectors in automated tests by mingzhu (@mingzhu) http://watirmelon.com/2011/08/09/death-to-xpath-and-css-selectors-in-automated-tests/#comment-3758 Thu, 16 Feb 2012 01:45:40 +0000 http://watirmelon.com/?p=1043#comment-3758 Need some special tag to display the code:

...
</div

]]> Comment on Death to xpath (and css) selectors in automated tests by mingzhu (@mingzhu) http://watirmelon.com/2011/08/09/death-to-xpath-and-css-selectors-in-automated-tests/#comment-3757 Thu, 16 Feb 2012 01:44:22 +0000 http://watirmelon.com/?p=1043#comment-3757 Hi Alister,

Thanks for the excellent article. It’s indeed very neat. However, I would question the flexibility.

Imagine we have
…..
and there a lot of inputs and links and text under the div.

If later the code implements a new interface, so we have “user-nav” changed into “menu-nav”. As in automated testing, we then need to go through all of our automation code and find any thing uses menu-nav and change that into user-nav. This would be so troublesome when it’s in transition phase, where some page is using new interface (“menu-nav”) and old interface (“user-nav”).

Cheers,
Ming

]]>