A Smattering of Selenium #59

Its been a month and a half since the last one of these, and the volume of links I have collected illustrates that. So this week is now a cleanup week.

• How Browsers Work: Behind the Scenes of Modern Web Browsers seems to be one of those articles that people who automate browsers for a living should be familiar with.

• 100% Test Coverage is always the goal.

• Continuous Deployment and Data Visualization reminds us that if some data is good, more is often better.

• This is for JUnit, but the ideas apply to any runner.

  JUnit Kung Fu: Getting More Out of Your Unit Tests

  View more presentations from wakaleo

• Database Cleaner is a set of strategies for cleaning your database in Ruby. I think you should just let your database get dirty (since that’s what happens in production) but I’ll give that there are scenarios where that’s not desirable.

• The Zen of UI Testing with Selenium, Hudson and Sauce Labs illustrates a nice switch in the @Before method to run either locally or in the cloud (in this case with Sauce Labs). Limiting your framework to be always in the cloud or always behind your firewall is silly these days.

• What’s wrong with Ruby’s test doubles? has good overview of the types of test doubles there are. Front-end automation should be generous use of the ‘Stub’ brand I think.

• Automation is programming. And Page Objects are OO. So How to Design Classes is pretty darn interesting.

• The Samuel L Ipsum really needs an API so we can use it as a random string generator for automation.

• For one project I’m working on, I am validating whats in the browser with a JSON feed. JSON Formatter has been a saviour the last week.

• Previous
• Next