Testing Less, Achieving More: How we mastered The Art of Strategic Testing
summary
Claims that testing less increases quality by focusing automated checks on a consolidated set of critical parts, defined as blockers regulatory requirements or business‑crucial flows. Implementation uses Typescript and Cypress and a test management tool called test tril. Process adds a quality‑assistance model, a 70/30 rule for automation vs manual work, and nightly + pre‑release runs. Results: regression time drops from ~1 day to ~1 hour and release cadence moves from weekly to daily.
AI-written summary · about
chapters (17)
- 0:00Strategic testing introduction
- 0:48Testing problem identification
- 2:15Three-step better testing
- 3:40QA team responsibilities
- 4:43Phase one details
- 5:47Critical parts definition
- 7:52Identifying critical parts
- 9:35Documenting critical parts
- 10:58Phase two automation
- 11:40New test engineer ways
- 13:04Robust test automation
- 14:30Automated test execution
- 15:56Post-improvement responsibilities
- 16:58Human impact of strategy
- 17:39Future API automation
- 17:59Key takeaways
- 18:20Q&A
related talks
18mEffective Test Automation Framework Design
58mTesting Strategy - New Model, Better Outcomes
21mThe Essential Pillars of Automation Testing for Success
35mBetter, Faster, Stronger - Delivering High Quality Products
34mesting in modern times: A story about quality and value
49mThe Secret to Successful Testing
22mTest Automation and Beyond: Implementing Continuous Testing Effectively
06mWhy do we need to test?