Selenium and Cucumber
summary
Shows how teams combine Capybara + Selenium 2 with headless drivers (Webrat) and HTML parsers (Nokogiri/Hpricot) to run CI in Hudson using the CI Reporter gem, and claims a real project has 12,000 integration features and ~200 Selenium scenarios with parsing time about 20–30 seconds up front. Demonstrates tags, multilingual step files, and PDF/receipt verification, and warns about duplicated steps, fragile regex step definitions, slower parsing and no editor autocomplete.
AI-written summary · about
chapters (28)
- 0:00Intro
- 0:22Dima Kovalenko
- 1:07Past Experience
- 1:26Disclaimer
- 3:12We don't need Automated Tests!
- 3:42Overview
- 4:05Assumptions
- 7:46The Stage
- 13:18Why automated tests?
- 14:23Who should be writing tests? • Developers • Unit, Integration, Functional
- 16:18Mind Map Solution
- 17:29Good Features
- 17:46Tags
- 19:35First run
- 20:28Write Step Definitions
- 21:05Multiple Test Drivers
- 22:21Selenium I support
- 23:05Selenium | Tip
- 24:28Selenium 2 support
- 24:43Capybara
- 26:43i18n Chinese
- 27:24Readable Test Results
- 28:30Hard to find Step Definitions
- 28:50Bad Features
- 29:33Conclusion
- 31:02Work @ Groupon
- 36:48Natural Language
- 41:47Regex Step Definitions
related talks
32mAll about web application testing
36mBDD With Cucumber
49mFront End Testing Frontier
25mWriting end to end tests with a smile
32mAmbitious Capybara
35mCucumber: Automating the Requirements Language You Already Speak
34mWriting end to end tests with a smile
37mSelenium In the Enterprise: What went right, what went wrong (so far)