Who should write automated tests?
summary
Examines who should write automated tests in teams with roles like testers, developers, automation engineers, and business analysts. Discusses whether having each stage handled by narrow specialists helps or harms effective creation and use of automated tests, aiming for a group discussion to analyze the issue.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 2:59Classic test automation
- 9:47Socialist automation
- 13:17Universal testing soldier
- 16:28Testing nihilism
- 20:38Unit tests: who writes
- 23:07Devs write tests
- 27:20Choosing testing criteria
- 30:32Q&A
- 34:29Team testing approach
- 37:43Time for tests
- 39:08Dedicated test engineers
- 40:46Testing reports and tools
- 41:29Q&A
- 42:36Summary
related talks
38mDo We Really Need A Test Automation Engineer?
44mTest Automation as a Development Team
09m"Testing is everyone’s responsibility.”
01h 12mThe Tester's Role: Automator vs Manual Tester
11mTechTalk "Automated Testing Inside the Team or as an External Service"
49mDoes software testing need to be this way?
37mWe Are The Testers: You Will Be Assimilated
55mShifting the Testing Role Pendulum