To cooperate or to betray? Decoding the tester's dilemma
summary
Argues that the Prisoner’s Dilemma maps to five concrete tester behaviours: choosing infrastructure work (new pipeline) over actual test coverage, picking marketable tools instead of fit, internal competition for visibility, org incentives that reward department goals, and short‑term fixes like adding thread sleep in Selenium that make suites unmaintainable. Recommends leader actions (set clear reference points, team/peer rewards, mandated cross‑team discussion) and individual remedies (reflect on long‑term tradeoffs, prioritize product users and teammates).
AI-written summary · about
chapters (7)
- 0:00Tester's dilemma
- 1:05Game theory and prisoners dilemma
- 6:12Prisoners dilemma effects
- 13:02Leaders fostering cooperation
- 17:34Fixing dilemma from leadership
- 23:02Individual strategies
- 25:45Q&A
related talks
36mWhole team quality: In the same boat or up the creek?
59mBabble & Dabble: Creating Bonds Across Disciplines
15mThe Tester I Was and the Tester I Could Be
40mThinker, Tester, Lawyer, Spy
10mTester’s Inferno: 5 Circles of Software Hell
37mUnderstanding the successes and the pain points of different testing strategies
31mStop Breaking Your Teams: Seeing the Whole Instead of Pieces
37mWe Are The Testers: You Will Be Assimilated