Test Driven Development for Embedded C (Pragmatic Programmers)

This is the perfect book for someone who is fluent in the C programming language and wants to learn test-driven-development for embedded systems / microcontrollers. I highly recommend reading The C Programming Language by Ritchie and Kernighan before this book. It is important to have a good understanding of the C language before reading this book.

Very good book.

One of the must reads for firmware development. Walks through some of the best practices and challenges thinking of old school firmware development methods where testing left to be done later.Lot of code and examples to walk with author.Warning: Its old book so coding together might be challenging, still very good to get celar understanding.

Lot's of examples to help the reader understand the concepts. I thought it would've been better if more coverage would've been given to working with the provided complex makefiles (via the downloads). If you're not really good at complex makefiles, it may be difficult to figure out how to make this work in your process. All in all though, a really good book. I thoroughly enjoyed reading it, multiple times.

This is a great book for anyone who wants to learn about Test Driven Development (TDD) and is focused on state-of-the-art development practices to produce high quality code (defined as code that does what it is designed to do). The book also describes how these unit tests fit into a broader test strategy (that includes other forms of testing) to ensure that features delivered are those desired/required by customers.As an Agile Coach, I have found this book to be an excellent addition to my library.

I am currently working on bringing modern development practices to an ARM embedded software project with legacy code. I have quite a bit of unit testing experience, and found myself still interested in reading the whole text and not just skimming. This book has been a huge help! It shows for example ways to intercept and test hardware I/O. Unfortunately some source code editing is required, but (realistically) how would you avoid that?

A good intro to the technique. I already practiced several of what they had examples of.Clearly written with good examples. Clear descriptions and examples of frameworks.Also see youtube videos of Uncle Bob for more.

I've heard people say that TDD is not for Embedded, maybe for Web but not for Embedded. James Grenning, does a great job at showing how it can work for Embedded and it will help reducing bugs. I definitely recommend this book!