Design patterns to boost your test automation
summary
Claims that familiar OO design patterns speed development, reduce late-found bugs, and make test code readable; shows concrete patterns and examples: Builder pattern decouples tests from constructors by creating Employee builders so tests pass only relevant fields; Decorator models UI variations with coffee example and lets AB-test components; Strategy swaps slow UI registration for fast API user-creation; Singleton centralizes config and webdriver but warns it’s often an anti-pattern; Page Object causes long classes and maintenance pain and Screenplay refactors tests into actor‑task‑question objects improving reuse and clarity.
AI-written summary · about
chapters (20)
- 0:00Welcome
- 1:12Meet the speaker
- 2:37Need for design patterns
- 4:02History and theory
- 8:22Design patterns vs SOLID
- 10:11Builder pattern for data
- 16:51Builder benefits
- 17:32Decorator pattern
- 20:02Strategy pattern
- 21:48When to use Strategy
- 22:31Singleton pattern
- 25:20Singleton drawbacks
- 26:04Page Object problems
- 27:28Page Object smells
- 28:50SOLID in Page Objects
- 31:19Screenplay pattern
- 34:07Screenplay improvements
- 34:49How to start using patterns
- 39:47When not to use patterns
- 41:10Summary and Q&A
related talks
45mDesign Patterns in Test Automation
40mRAMP up your testing solution: test automation patterns
25mTest Craftsmanship: Clean code practices for Test Automation
53mAdvanced Patterns for Automated UI Testing
36mLiving on crotches or UI Automation antipatterns
49mAn Easy Way to Automate Complex UI
44mTesting the untestable - patterns and use cases analysis
32mLiving on Crotches or UI Automation Antipatterns