22. May 2015 by Michael Wowro
For me the benchmark for XPath tools is the FirePath for Firefox, which fits IMHO perfectly the needs of testautomation.
My criteria for a good xpath tool:
1.) Showing the DOM (for good orientation)
2.) Suggesting a proper xpath for an element (ideally it’s good enough to use it without modification):
3.) Alert when xPath is invalid (in contrast to not finding an element)
4.) and of course the basic stuff: usability, reliability (…)
Now I’m looking for an equivalent for Chrome browser and found 3 xpath extensions in the Chrome Webstore:
The XPath Helper is the most distributed extension with 250 feedbacks, so I installed this tool first. After you press ctrl+shift+x, the tool appears on the TOP of the viewport, which is unusual for me, but ok. Very nice is the handling, to get the xPath for an element: you just have to press shift, while hovering over the element. Also an invalid xPath is alerted well. But the suggested xpath is much too long, so must be modified by hand in every single case. Additionally I’m heavily missing the virtualisation of the DOM, like in FirePath.
While playing around, I quickly found a severe bug: This xPath “//*[@class=’gsfi’]” shows a match for this element: class=”gsfi xh-highlight”. Evil.
The second choice with 96 feedbacks is “XPath”, which comes with the unattractive total rating of 2 of 5 stars, but let’s see. After installing it, it opens two tabs just for advertisement, which is not really sympatic, but let’s see. As claimed I clicked on the toolbar icon and then clicked an element. I did it very often, but nothing happens. To check if I’m too dumb to use it correctly, I read the ratings in the Chrome Webstore: many users facing the same simple problem: this tool just doesn’t work.
The third choice with tiny 10 feedbacks is xPath Analyzer, but let’s give underdogs a chance. After installing I found, this tool also comes with an icon in the toolbar. Trying to use it on www.google.com I got an error: “This page does not contain an XML document.” Not wasting much of my time, I estimate: this tool has no use for testautomation.
Last chance to find an alternative to firebug in Chrome is asking stackoverflow: In this answer it’s indicated, that for Chrome the best choice is to use the build-in Chrome Developer Tools to cope with xPaths.
I found, the suggested xPaths are good. Anyhow, to get the xpath from an element is pretty inconvenient:
1.) First you have to “inspect the element” via context menu.
2.) Then you have to “Copy XPath”
3.) and finally paste it manually in the DOM searching panel:
Unfortunately Developer Tools don’t tell me, if my xpath is invalid or just no element was found. This slows down the debugging. Another drawback in terms of usability is, that while writing the xPath, the focus in DOM may jump away.
There’s no such thing like FireBug in Chrome ecosystem. However if you must use a xpath tool in Chrome use the build-in Chrome Developer Tools.