TDD for Testers workshop
summary
Shows a small Python credit‑rating kata implemented with unit tests and slower Selenium UI tests, exercising rules like minimum 0, doctor/lawyer/accountant => 50, default 20 and “>7 credit cards => -5”. Demonstrates TDD as red–green–refactor driving design, code on GitHub, and that unit tests run far faster than end‑to‑end. Argues testers add upfront acceptance criteria, exploratory scenarios and stop redundant tests; notes ~50 combinations exist but a focused suite of 10–15 tests often suffices.
AI-written summary · about
chapters (12)
- 0:00Start
- 1:13Welcome
- 3:03Red Green Refactor
- 4:08Integration and Unit Tests
- 4:24Integration Test
- 11:26Assert
- 23:13Passing Tests
- 26:15Test Cases
- 29:47Upfront Acceptance Criteria
- 32:16Redundancy
- 40:31How Much Acceptance Criteria in a Story
- 43:02Why Use Selenium Tests
related talks
02h 21mWorkshop: Introduction to Testing in Python
37mTDD - the why, the how and the when not
48mTDD - It's About More Than Just the Tests
28mTDD for Absolute Beginners
21mHow TDD and CDD make your apps suck less
10mWrite Better Tests With TDD
55mTDD and the Terminator - An introduction to Test Driven Development
01h 13mTDD Revisited