Scaling Automated Testing & Architecture from Startup to Enterprise
summary
Started with slow flaky UI tests backed by a home appliance simulator and switches from MVVM to clean architecture, then breaks an 800k‑line monolith into feature‑based modularization. A newly formed core team owns CI/CD, refactors high‑error and frequently changed areas first, and injects mocked dependencies for unit tests and mocked external deps for module integration tests. Build + test time drops from ~45 to under 20 minutes, flaky failures fall to about 5% of runs, and confidence in automated releases returns.
AI-written summary · about
chapters (7)
- 0:00Automated testing evolution
- 7:16Testing strategy failures
- 12:32Building core team
- 19:42Clean architecture switch
- 24:24Modularization improvements
- 31:31Testing transformation takeaways
- 33:23Q&A
related talks
53mTransforming testing methodologies: From manual to robust strategies
43mTransformative Culture
40mScaling testing & test automation without losing control
40mThe Build That Cried Broken: Building Trust in Your Continuous Integration Tests
49mThe Whole Team Approach to Testing in Continuous Delivery
32mClimbing the Mountain of CI/CD: A Tester’s Tale
45mBuilding a successful test automation architecture in a microservices environment
31mThe Build That Cried Broken: Building Trust in Your Continuous Integration Tests