End the Test Engineer role: how cross functionality leads to a better engineering
summary
Argues to remove a dedicated test-engineer bottleneck by teaching cross-skills so developers write end-to-end tests and testers ship code, with concrete examples: Angular 1.x app, Protractor tests in TypeScript with Jasmine/Karma, CI and device-farm automation, and measurable effects like regression cycles longer than a week shrinking to same-day verification. Describes building a shared test suite, who owns which checks, and how this increases velocity, reduces late bugs, and improves inclusion.
AI-written summary · about
chapters (7)
- 0:00Start
- 4:20Summary
- 7:30Test Engineers can struggle
- 9:45Encourage growth
- 11:44We are responsible
- 12:56Apply new skills
- 13:46Exclusivity hurts
related talks
47mFull-Stack Test Automation
27mThe Effective Development - End (What) End
12mBeyond Testers: Embedding Test Expertise in Modern Software Development Teams
27mTest Effective Development - End 2 (What) End?
30mEnd to End Testing: The Game Has Changed
45mEnd-to-End Test Architectures, a Dead End Road
41mEnd-2-end testing without the pain
45mHow to Make Developers LOVE Writing e2e Tests