Test Craftsmanship: Clean code practices for Test Automation
summary
Claims that applying SRP, DRY, LoD to test automation yields faster time to market, lower maintenance and fewer false results, with concrete examples using Selenium WebDriver, Playwright, Cypress and Selenium Grid and WebDriver for parallel runs. Evidence includes refactoring demos where AI-produced code scores shift from 4 to 8 to 9, warnings about monolithic regression suites (regression pack taking 6 hours or even two days), and pragmatic moves beyond Page Object to durable design patterns.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 2:15Talk overview
- 3:38Test authoring strategies
- 5:25Small functions in tests
- 6:51Fast feedback loops
- 8:38Context over models
- 9:21Campsite rule and TDD
- 10:03Test maintenance
- 11:06Beyond page objects
- 12:09Refactoring vs rewriting
- 13:15Code quality metrics
- 14:39Law of Demeter
- 15:41Test execution parallelization
- 16:24Avoid cleverness
- 17:46AI and test craftsmanship
- 19:13Q&A
related talks
48mDesign patterns to boost your test automation
51mRedefining test automation
39mPanel Discussion | Mastering Test Automation: Strategies and Innovations
14mTest Automation Framework Design and Implementation
47mThe Valley of Success
21mTest Kitchen: A Recipe for Good Tests
21mThe Essential Pillars of Automation Testing for Success
54mTest Automation Transformation Avoiding the 7 Common Pitfalls