Self-Generating Test Artifacts for Selenium/WebDriver
summary
At Peoplefluent test maintenance overhead drops from ~40% to under 3% by generating Selenium Page objects at build time using Java reflection to parse Velocity and JSP source, producing base page classes plus hand-edited derived pages. The generator parses Velocity and JSP to extract IDs and element types and the build causes compile-time failures to block bad checkins so developers fix breakage before tests run. Outcome: ~1,900 WebDriver tests run at about 98% pass rate and far less ongoing maintenance.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:07Reactive trap in test automation
- 3:13From page objects to automation
- 7:08Self-generating page objects
- 7:52Demo: worst web page
- 12:18Automated page regeneration
- 17:01Handling new UI flows
- 20:36Advanced features in models
- 22:20Developer integration
- 24:28Results and maintenance
- 26:53Self-testing pages
- 28:18Defect discovery impact
- 30:04Masking issues concerns
- 31:50When to implement
- 32:11Source code characteristics
- 33:40Parser system details
- 36:53Drawbacks and challenges
- 38:38Gradual adoption
- 40:01Developer collaboration
related talks
01h 14mContinuous Testing
37mAutomated Performance Testing With WebDriver
30mRevolutionizing Continuous Integration with Selenium
42mReliable and Maintainable Webdriver Tests
05mTaming the Testing Beast
38mFreeing up Selenium
41mFunctional Tests (Selenium) in Practice
33mBringing Selenium to the Rest of the Company