Put the Knowledge to Work

  1. Think of 100 reasons why TDD could never work for you. Then go review your bug list.

  2. List bug root causes, and consider which of them might get prevented by TDD.

  3. Pretend that TDD might work for you and try it.

Footnotes

[16]

Greg Williams, Mark Karlesky, and Mark Vander Voord

[17]

Michael Feathers, Bas Vodde, and your humble author

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.