Advanced Patterns for Automated UI Testing
summary
Estimated manual regression takes 7–8 days so the team automates browsers with Canopy and Selenium and focuses UI tests only where lower‑cost tests can’t prove behavior. Concrete patterns include a page object pattern with a base class and go‑to methods, a library of data creation helpers plus a cache‑flush endpoint, and component test harness pages. Tradeoffs and rules for prebuilt vs on‑the‑fly data govern what gets tested at the UI level.
AI-written summary · about
chapters (9)
- 0:00Start
- 3:33Today's agenda
- 13:46Setting up a Ultest
- 17:01PageObject (it's not just for "pages"!)
- 28:354 rules for using pre-existing test data
- 40:23Test Data anti-pattern
- 43:41Refactor Ul code to make it unit-testable
- 46:42Use Ul-test-specific CSS classes & IDs
- 48:42Components + Test Harnesses = WIN
related talks
48mDesign patterns to boost your test automation
45mDesign Patterns in Test Automation
49mAn Easy Way to Automate Complex UI
32mLiving on Crotches or UI Automation Antipatterns
36mLiving on crotches or UI Automation antipatterns
45mUI Automation: Keeping Pace with Product Evolution
40mRAMP up your testing solution: test automation patterns
56mThe End Game