Test automation for developers
summary
Argues that test automation is for developers too and its real value is preventing defects by enabling continuous refactoring backed by fast reliable tests; introduces the explicit idea of a test scope (pick which components to exercise, mock the rest), promotes acceptance test-driven development with executable acceptance criteria, shows unit-vs-system tradeoffs, demonstrates a product‑promotion claim test as an example, and recommends jMeter for load testing.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 1:29What is test automation
- 1:58Testing vs quality
- 4:10Unit tests vs system tests
- 9:05Test pyramid
- 10:05Testscope
- 12:47End to end test
- 15:26Purpose of test automation
- 15:37Do we need test automation
- 16:09Why was the purpose of test automation
- 16:45Problems in the code structure
- 18:13Refactoring
- 20:02Simple design
- 21:44Unit tests
- 23:07Kent Beck rules
- 27:41Unit vs observable behavior
- 29:00Test structure
- 30:15Test claims
- 31:21Test example
- 32:53Tips for test automation
- 35:44Testdriven development
- 40:53Conceptions misconceptions
- 43:37Pyramids
- 45:01Summary
- 46:18Questions
related talks
32mWhy testing is a developer's problem
38mDo We Really Need A Test Automation Engineer?
51mRedefining test automation
44mTest Automation as a Development Team
48mTest Automation - A Systems Thinking Approach
42mUse testing to Develop Better Software Faster
55mShifting the Testing Role Pendulum
48mTesting is Confidence - A Developer's Perspective