We Are The Testers: You Will Be Assimilated
summary
Proposes to flip the ratio from many devs per tester to teams with one or two developers and four testers — a test architect, test engineer, analyst, enhancement specialist — and claims that yields issue cleanup, better coverage, proactive inspection, reduced key‑person risk and quality‑focused production. Recommends concrete practices: use a test improvement backlog (Jira), itemize risks by role, build tooling and automation, map system knowledge visually. Proposal rests on practitioner experience not formal research; some pilot examples are anecdotal.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:22Traditional testing problems
- 9:09Why testing needs specialization
- 11:56Tester types and roles
- 17:34New tester team structure
- 24:59Quality over volume
- 31:22Pitching and implementing change
- 32:49Call to action
- 33:11Q&A
related talks
38mRick Tracy: The Future Fo(u)r Testers
36mWhole team quality: In the same boat or up the creek?
33mAgile Software Testing
08m“Testers! Aim to Enable”
59mBabble & Dabble: Creating Bonds Across Disciplines
49mDeveloper + tester = quality++
34mHelping Testers Add Value to Agile Projects
09m"The Tester’s Role: Balancing Technical Acumen and User Advocacy"