Test Driven Development
Topic Overview: How do we make TDD work, and what is it good for?
Convenor or Lecturer: JimCoplien
Participants: Participants: Please add your name here. I spaced out and forgot to take a list!(if you put your Namepage here, people can click to see how to contact you.
Session Notes:
- Good TDD is always preceded by a good design foundation--a fact missing in most TDD presentations
- For TDD to be Agile, the up-front design must be lightweight
- Integration-level or system-level TDD provides a tracible path to user requirements
- Different tests solve different kinds of problems: unit tests, integration tests, acceptance tests, performance tests, usability tests...
- Unit-level TDD has some problems:
- It often cannot be traced to any external user need
- It is usually reflects what the coder is thinking up at the time, rather than being driving by a customer at hand
- It emphasizes procedural behavior and makes it difficult to "think like an object"
- Having up-front design foundations can solve some of these problems
Note that Sadek Drobi has posted pictures of the handwritten flipchart notes from this session!
| 