Pragmatic TDD
summary
Shows a hands‑on workflow using PHPUnit to build a league standings service: write failing tests, implement record/getStandings, extract TeamStanding, then refactor with a rulebook interface to support old and new tie rules. Demonstrates mock objects to avoid heavy setup, runs focused unit tests, and proves changes by green tests. Codebase ends with passing suites, a concrete advanced‑rule implementation, and examples of where coverage and pragmatic TDD catch regressions.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 7:09Software testers
- 13:33Code coverage
- 16:17Testing tools
- 20:56Does testing improve your code
- 22:25How to write tests
- 23:18Workshop
- 26:28Teams
- 27:28Standings
- 29:28Setup
- 32:28Result
- 35:28Fix
- 39:28Counter
- 48:58Scoring
related talks
01h 00mPrinciples of Unit Testing
56mUnit Testing by Example
55mTest to Break Principles
57mWhy Your Test Suite Sucks
29mEffective tests and testing effectively
52mWriting Unit Tests Using PHPUnit
58mTDD for database related code, how is it possible?
01h 04mTest Driven Development with C# - from Padawan to Jedi
