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.
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.
Good job covering the changes through IE generations of its supposedly future-proof versions.
The only reason in my opinion that IE will continue to be strong in the market is its proprietary ties to the operating system. Which will also remain its most vulnerable point.
Works same in the head. All scripts if not set to asynchronous will prevent further rendering of the page until the script has finished loading and running.
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!