Knowing your automation
summary
Describes building and using UI automation around Selenium/WebDriver, starting from keyword-driven spreadsheets to custom wrappers and a 2013 in-house framework; shows drop down to WebDriver is essential because higher-level libraries (Capybara, Protractor, Selenide) spawn extra HTTP calls and hidden commands, adding surprising runtime and flaky behavior when run remotely (Sauce Labs). Demonstrates fixes: extend element finders, use composition over inheritance and builder/domain objects, and warns that implicit wait cost makes conditional checks expensive. Overall wrappers help but leak.
AI-written summary · about
chapters (20)
- 0:00Automation abstractions
- 1:08Test automation examples
- 2:15Leaky abstractions
- 3:20Legacy automation tools
- 5:07Keyword-driven pitfalls
- 7:15Refactoring automation
- 8:19Selenium RC to WebDriver
- 9:23Page objects challenges
- 10:48Leaky abstraction costs
- 12:12Custom automation frameworks
- 13:41Third-party wrappers
- 15:10Conditional logic costs
- 15:55Behavior objects in automation
- 17:44Builder patterns for data
- 18:48Extending abstractions
- 20:57Vendor automation trends
- 22:46Codeless tools
- 24:10Modern black box testing
- 25:00UI automation decline
- 26:06Q&A
related talks
35mBuild an automation framework... with a developer mindset
46mTest Automation with Selenium WebDriver, Java, and JUnit
32mAll about web application testing
39mTesting web apps with Selenium
45mUI Automation: Keeping Pace with Product Evolution
01h 14mContinuous Testing
48mChallenges in UI Automation and How to Solve Them
07mInterview with Neil Manvar