Testing Processes, One Size Does Not Fit All
summary
Argues that company-wide testing processes migrate through three concrete stages—standard → specializations → static individual → dynamic living—with teams adopting context-specific steps (examples: staging envs, testing in production, choosing tools like Cypress or “automating everything” or nothing). Lists measurable benefits (reduced overhead, faster local experiments, stronger ownership) and real risks (lost audit trails for security/government contracts, steeper ramp for transfers, broken cohesion). Recommends documented team processes, quarterly reviews, communities of practice and shadowing to keep organization aligned.
AI-written summary · about
chapters (7)
- 0:00Intro
- 1:53What are individual team processes
- 3:20Benefits of individual processes
- 8:25Indicators of a potentially bad fit
- 11:47What are you going to do
- 16:41How to maintain cohesion
- 19:52Wrap up
related talks
57mOptimizing Your Testing Team
16mChallenges of Testing at Scale | Experiments and Experiences
58mTesting Strategy - New Model, Better Outcomes
37mUnderstanding the successes and the pain points of different testing strategies
09m“Leading a Testing Revolution”
37mTransforming Testing from a Task to a Strategic Mindset
36mWhole team quality: In the same boat or up the creek?
18mEffective Test Automation Framework Design