Repeat Until Done
The core of the driver is in place. The turn on and turn off functionality works top to bottom. Now you continue adding tests and production code until all the meat is on the skeleton. Let’s look at the updated test list in Figure 6, LedDriver test list—evolved.
I’ve crossed off the completed tests and also added tests that were not originally anticipated, at least not to the level of detail that TDD drove us to. Test lists evolve; it’s expected, and there is nothing wrong with it. As we dig in, we learn more, and the ideas for new tests come as a consequence of our evolving understanding. ...
Get Test Driven Development for Embedded C 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.
