Abstract
Selenium, the open-source web application black-box testing tool, is very powerful, and very dangerous. What are the potential benefits and dangers? How do you determine when to use it, when not? How do you determine how to use it, and how not?
I’ll cover healthy and unhealthy patterns for using Selenium. This includes cultural and interpersonal patterns, strictly technical patterns, and “testing-triangle” “Definition-of-Done” patterns. I’ll discuss how Web 2.0 trends (especially dynamic HTML of all kinds) effect Selenium testing and all web app testing.
I’ll also discuss where the Selenium project is headed, why, and how long it will take to “get there.”
Bio
Patrick Wilson-Welsh, has over 30 years of professional software development experience, I’ve worn a lot of hats. Over the last 7 years or so I’ve worked as an agile consultant, specializing in building development teams, and training and mentoring them in agile development and agile testing practices. I’ve worked mostly in Java. Currently focusing on Storytesting as a struggling agile practice meme. I am employed by Pillar Technology, a growing group of software craftsmen in Michigan, Ohio, Indiana, Atlanta, and Boston.
|