A Smattering of Selenium #62

All opinions, all the time…

• It all began with Test Design for Automation which lead to Automated Test Design (riffing/ripping off Alan Page)
• And then through some weird Jedi mind control there was Design for *GUI* Automation which in turn led to more UI test design (once more from Alan Page)
• And heck, why have two articles from the same author when you can have three?! It’s (probably) a Design Problem — though I don’t think Chris has riffed off this one yet…
• Remember, Not Every Test Should be Automated!
• Dependency Injection Is NOT The Same As The Dependency Inversion Principle — not that I really understand either really…
• Who knew a collection of scrapebookers is called a ‘crop’? Also, a ‘scrapbooking consultant’? — automation is hard, let’s go scrapbooking! Anyways, Taking on Water is dead on in terms of which things to prioritize when automating.
• Improving the Maintainability of Automated Test Suites by Cem Kaner is an older paper, but the Strategies for Success on page 3 are important. Especially 1, 2 and 5.
• Also from the vaults is Harold’s Corollary to Knuth’s Law which is aimed at Unit not Functional tests, but still is food for thought.
• Why Continuous Deployment Matters
• The Little Black Book on Test Design is meant for exploratory testing, but I bet there is stuff one could pull out of it for automation purposes as well.