Part 1. DDT vs. TDD
"Let the developers consider a conceptual design," the King said, for about the twentieth time that day.
"No, no!" said the Queen. "Tests first—design afterwards."
"Stuff and nonsense!" said Alice loudly. "The idea of writing the tests first!"
"Hold your tongue!" said the Queen, turning purple. "How much code have you written recently, anyway?" she sneered.
"I won't," said the plucky little Alice. "Tests shouldn't drive design, design should drive testing. Tests should verify that your code works as it was designed, and that it meets the customer's requirements, too," she added, surprised by her own insight. "And when you drive your ...
Get Design Driven Testing: Test Smarter, Not Harder now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
