Many Hats to Make a Tester
summary
Claim: testing duties must be split across a whole team, not one person, with concrete roles and measurable costs. The team maps 15 hats (examples: product historian, on-caller, parafunctionalist, feature shaper), runs Appium automation against a device farm, and spends major time on pipeline maintenance — the pipeline was green only 4 out of 22 days. Example composition: five system testers + ten developers = 15 people sharing these responsibilities.
AI-written summary · about
chapters (7)
- 0:00Intro
- 1:37What is a Tester
- 6:40The Role of a Tester
- 10:09The Tester Hat
- 16:58Labels
- 18:11Job Crafting
- 20:23Questions
