Seven Fundamentals Of A Successful Testing Team
summary
Seven concrete steps for building a testing org, with a claimed methodology called METS minimal essential test strategy, a focus on automate critical tests (no percent targets), and concrete tooling examples: Selenium, Postman, BrowserStack, Jenkins and the Elastic stack for historical analysis. Expect practices like running suites daily, the “go for green” rule of running a new automated test five times for consistency, advice on flaky tests and the ROI roller coaster and how to trace automation back to manual cases.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 3:14Why software testing matters
- 6:01Common testing vocabulary
- 8:49METS methodology
- 13:01Test plan execution
- 17:40Testing foundation traps
- 19:25Test automation fundamentals
- 25:23Automation ROI reality
- 32:02Flaky tests and traps
- 35:36Scheduling automation
- 38:44Flaky test pitfalls
- 40:31Partnerships and avoiding the software police trap
- 42:18Final thoughts
related talks
57mOptimizing Your Testing Team
54mTest Automation Transformation Avoiding the 7 Common Pitfalls
39m4 Pillars of Successful Agile Test Automation
11mNeed For Tests: Most Wanted
58mTesting Strategy - New Model, Better Outcomes
14m8 Principles for Selling the Value of Professional Testing
18mEffective Test Automation Framework Design
25mTesting Processes, One Size Does Not Fit All