An overview and history of the Selenium web application testing tool, by Selenium's creator Jason Huggins. Presented on April 25, 2009 at JSConf in Arlington, Virginia.
http://jsconf2009.com/speakers.html#huggins
17. ThoughtWorks Time &
Expense
Source: - Neal Ford: http://nealford.com/downloads/conferences/2006_nfjs_canonical/Neal_Ford-Testing_with_Selenium-slides.pdf
18. First Attempt -
JWebUnit
• Simulates the browser
• Can’t handle browser-specific bugs
• Can’t handle JavaScript in the DOM
19. Second Attempt -
DriftWood
• Mozilla extension (never published)
• Pro:
– Drove a real browser, so it could handle
JavaScript UI features
• Con:
– Not for IE or Safari :-(
– XML Syntax for tests. Yuck!
20. Third Attempt - JsUnit
• Pro:
– Can test JavaScript in the browser!
– Works in Mozilla/Firefox, IE, and Safari!
• Con:
– Emphasis on single-page unit test (no
page-to-page workflows)
– Couldn’t see what it was doing
26. Forking FIT
• Selenium initially was an attempt to
implement “FIT for web browsers”
• Ended up forking:
– Wanted to see what the browser was doing
– Wanted a richer API