3 ms·
> The binding is on a layer that humans don't see, and it makes it fragile. And that seems to be part of the point of this project. From the description: > In
by cowsandmilk 7y ago
> The binding is on a layer that humans don't see, and it makes it fragile.
And that seems to be part of the point of this project. From the description:
> In Selenium, you need to use HTML IDs, XPaths and CSS selectors to identify web page elements. Helium on the other hand lets you refer to elements by their user-visible labels.
The example script uses a bunch of user-visible labels, not classes, ids, ancestors, etc. It is things like "click('Sign in')" which you would tell a user you were walking through an interface.
- bauerd 7y agoThis works fine until it does not, for example when dealing with custom UI controls, which is when reality sets in and you find yourself wrangling HTML IDs, XPaths and CSS selectors again.
- ethbro 7y agoIn worst cases, I always tell people to bind to user-visible elements, then only navigate the local DOM from there. Global XPath type traversal is fragile, unless you're plugged in enough that the dev team lets you know when they break it.