I would suggest also allowing CSS selectors as a fallback. Text changes often whereas a selector will change less often, producing a more reliable point of interaction.
I would also suggest you put a screencast of a hello world. With many people new to testing using headless webkit, they may have the wrong perception of how selenium tests are run. Additionally what may not be obvious to people used to javascript-based headless webkit tests is that Selenium/Helium tests are written in python. Might want to clarify that as well.
thanks for the suggestions! I'll discuss them with my colleagues.
CSS selectors are supported, because Helium is fully compatible with Selenium. Eg.: You can say click(driver.find_element_by_css_class('btn')), where click(...) is a Helium command and driver.find_element_by_css_class(...) is from Selenium. Helium and Selenium are 100% interoperable.
The infrastructure for plastic cards will be around for a very long time. I think the author is ignoring the very expensive need for infrastructure changes. It's the same reason why everyone isn't driving around electric cars.
I love the recent focus on hiring people, not job descriptions. I saw another article written by David Cancel of Performable on the same subject. Technical skills are important, mind you, but personalities can't be taught.
I would also suggest you put a screencast of a hello world. With many people new to testing using headless webkit, they may have the wrong perception of how selenium tests are run. Additionally what may not be obvious to people used to javascript-based headless webkit tests is that Selenium/Helium tests are written in python. Might want to clarify that as well.
Good luck!