Alex Pshe: 13 Best Practices for Building Web App Test Automation from Scratch
summary
Practical checklist: evaluate automation complexity with concrete questions (endpoints, platforms, CRUD coverage), confirm review apps and reproducible API controls, and measure ROI using his example math (90 hours setup, 8 hours weekly maintenance → nine years ROI at 4 releases, two years at 20). Prefer backend-language tests to reuse models, generate test data via reflection, design scalable generic services instead of entity-specific code, enforce environment cleanup, parameterize runs, use smart state waits, and gate everything in CI/CD with unit, API, UI and performance checks.
AI-written summary · about
chapters (13)
- 0:00Web app test automation intro
- 4:51Assessing automation complexity
- 9:14Evaluating testability
- 12:46Calculating automation ROI
- 17:48Choosing automation tech stack
- 20:21Test data preparation strategies
- 22:06Scalable automation frameworks
- 28:12Environment consistency
- 29:38Parameterizing test configs
- 31:06Smart state waiting
- 33:36CI/CD integration
- 38:1913 best practices summary
- 39:22Q&A
related talks
53m20 QA Best Practices to take back to your workplace
40mThe Test Automation Firehose
18mEffective Test Automation Framework Design
51mRedefining test automation
08mReviewing your test automation strategy"
54mTest Automation Transformation Avoiding the 7 Common Pitfalls
46mThe Practical Automation Playbook
13mBeyond the hype: What test automation really costs