August 8, 2011 by adam goucher
A Smattering of Selenium #57
Phew. The links made it through the Lion installation.
- Distributing the Same Test to Multiple Processes shows a technique for debugging flaky scripts
- Repeat after me: I will not automate GMail unless I am Google. Or if you will, you will do something like what is described in Verify email confirmation using Selenium. Notice that they are not using Se for it.
- Selenium and Nagios is something more teams should do I think.
- ‘This started out as a…’ usually means the discovery of a rabbit hole. Towards better acceptance test automation… has a great diagram where all roads lead to accidental complexity and The A Team the proposes solutions to those complexity problems.
- Specialized Skills remarks that ‘life is like a box of crayons’ — I’ve been having this conversation around automation again recently. When everyone blurs their specialization boundaries you have a [chance] of success.
- Performance Testing Practice Named During Online Summit names a practice we’ve often used — User Experience Under Load
- Introducing page-object gem showcases a pretty nice looking gem.
- Often people link to W3Schools.com when explaining XPath, CSS, etc. Please don’t. W3Fools explains why.
- Is there another Se-in-the-cloud provider coming? The testingbot gem seems to imply so
- FluentLenium lets you write JUnit scripts that look like JQuery code
- Mining Cucumber Features has a cool investigation trick that could be adopted to larger scopes than just cucumber
- Image to CSS Conversion with Img to CSS API is likely something I would explore if I was going to compare page image contents.
- Selenium IDE I think runs afoul of the attractive nuisance doctrine
- Are you a tool vendor? Here are some steps you can take to avoid a curse being placed upon you
- Test automation that helps, A Guardian Content API example is a bit of an exploratory automation experience report but also reminds that the point of all this is to get new information.
- Your Chrome browser might not be using HTTP anymore is my new Example One for why the browser vendors need to be the ones to provide the automation hooks. Which in this case, they do.