Orchestrating Your Testing Process - Coordinating Your Manual and Automated Testing Efforts
summary
Argues that the real outcome is an orchestrated testing process not separate silos and shows concrete numbers and behaviors: organizations run 5–7 automation tools and about 90% have CI, automation produces orders of magnitude more runs and focuses on stability while manual testing focuses on discovery. Recommends master planning, a center of excellence, one repository and a single integrated quality dashboard to consolidate fragmented reports, mandate refactoring, and make integration a first-class effort rather than a side job.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:07Why this talk matters
- 3:54Manual vs automated testing
- 6:22Automation relevance now
- 13:41Manual vs automated differences
- 18:38Automation myths
- 25:40Testing management challenges
- 27:04Test orchestration concept
- 28:09Master planning in orchestration
- 30:57Coordination in testing
- 31:59Single framework importance
- 33:03Quality dashboards
- 35:06Balancing integration and innovation
- 37:34Separate QA teams
- 38:35Future of testing
related talks
38mDo We Really Need A Test Automation Engineer?
57mOptimizing Your Testing Team
40mThe Test Automation Firehose
21mThe Essential Pillars of Automation Testing for Success
09m“Guide to creating your test automation strategy”
01h 48mNo Such Thing as Manual Testing and Other Confusions
55mShifting the Testing Role Pendulum
51mRedefining test automation