Mock Objects: Design Style and Process

A talk given to 4th year students at the Department of Computing, Imperial College. Some history of TDD, mock objects, and ruminations on what happened next.

Transcript

1. Mock Objects Nat Pryce Design Style & Process
2. A Web of Collaborating Objects
3. "Train Wreck" Code
4. Tell, Don't Ask
5. How to test an object that you cannot ask?
6. "Mock" its Collaborators
7. Ports and Adaptors
8. Start with the domain? Spoilers: No.
9. Work Edge to Edge
10. Start with a Walking Skeleton
11. Make Testing Easy* * This might be quite difficult
12. "The real value of tests is not that they detect bugs in the code, but that they detect inadequacies in the methods, concentration, and skills of those who design and produce the code." C. A. R. Hoare How Did Software Get So Reliable Without Proof? Lecture Notes in Computer Science vol 1051 1996 pp. 1-17