Many Hats to Make a Tester
summary
Claims that testing work splits into 15 hats across a team of 15 (five testers + ten developers), not one role; lists concrete hats like product historian, on-caller, parafunctionalist, feature shaper and test automation developer; describes building and maintaining pipelines and a device farm using Appium for cross-platform mobile automation; reports the CI radiator is green 4 out of 22 days (up from 1/22) and warns pipeline upkeep can take roughly half a year of effort if neglected.
AI-written summary · about
chapters (14)
- 0:00Appium Lite Conference welcome
- 1:47Why tester hats matter
- 3:14Expectations in testing role
- 8:12Myth of single tester role
- 10:44Distributing testing hats
- 11:50Core hats for test automation
- 12:55On-call and designer hats
- 14:41Pipeline maintenance hat
- 15:46Device farms and environments
- 16:27Collection hat and teaching managers
- 17:08Product historian and para-functionalist
- 18:10Unit development and technical roles
- 19:12Job crafting your role
- 20:37Q&A
related talks
55mShifting the Testing Role Pendulum
37mWe Are The Testers: You Will Be Assimilated
07mTest Camp
38mRick Tracy: The Future Fo(u)r Testers
38mDo We Really Need A Test Automation Engineer?
32mWhy testing is a developer's problem
55mTest Management Revisited
59mAgainst a Harmful Divide: Testing as the Lifeblood of Development