Plan Automation with 5% Rule: The Incremental Approach
summary
Claims a repeatable 5% Rule milestone: deliver at least 5% new automated coverage per short period (week/month/quarter) and iterate. Uses a quarter-based model with one-function-at-a-time roadmaps, weekly syncs, prioritized test suites, and explicit validation of manual test cases. Measures progress by percent coverage, marks un-automatable tests, schedules maintenance break deep code reviews, and reports that a small team (about 2.5 automation engineers) exceeds the 5% targets in iGaming, improving reliability without burning out. Validate test cases
AI-written summary · about
chapters (16)
- 0:00Incremental automation planning
- 2:36Stress points in test automation
- 5:50Gaps in automation collaboration
- 9:24Involve all roles in planning
- 11:55Prioritizing business priorities
- 14:25Validating test cases
- 16:54Prioritizing test cases
- 20:29Realistic deadlines and milestones
- 22:39Start with 5% coverage
- 24:05Refining automation roadmap
- 27:42Tracking test cases
- 30:54Maintenance and quality assurance in automation
- 33:51Calculating test coverage
- 35:17Evaluating strategy success
- 37:05Automation value over volume
- 38:50Q&A
related talks
46mBreaking Automation Rules for Better Efficiency and Coverage
21mThe Essential Pillars of Automation Testing for Success
17mStaying Ahead: The Future of QA Leadership
46mThe Practical Automation Playbook
45mImproved Regression Testing in Agile
24mWhen less is more –Applied statistics and Pareto rule for test automation
55mShifting the Testing Role Pendulum
19mBusiness Impact Delivery Using Test Automation