Test Driven Development for Embedded C (Pragmatic Programmers)
R**.
This book delivers.
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.
K**I
I can recommend.
Very good book.
S**S
Very readable and helpful!
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?
D**.
Pretty darn good book...
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.
M**T
A good method of writing code
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.
K**N
Must read for intermediate Embedded system programmers
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.
A**R
Essential for Any Lean/Agile Team
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.
E**.
Great book for Embedded Developers
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!
G**Y
All meat, no fluff. Still The Big Cheese when it comes to TDD for embedded systems!
I bought this book here ten years ago, and recently remembered that it was still on my to-be-read pile. So I finally read it, and I sure wish I'd done so long ago! A quick online search revealed that this book is still one of the only print resources on putting the two great tastes of Test-Driven Development and Embedded Systems together into one tasty treat.It's not a large book, but it is packed with meaty information. No fluff or filler in there as far as I could tell, since I found almost every page informative, and many pages set off various light bulbs in my head.I had a slight advantage in that none of the concepts were new to me -- I've been studying Object-Orient Programming since the early 90s and all the concepts that came along afterward, such as TDD, the SOLID principles, and so on. What I lacked up until now were concrete examples that could bring those concepts together in my head in a way I could actually apply. For instance, I finally really 'got' OOP programming just a few years ago, after trying to apply those principles to my software and firmware on and off for decades. At that point I had finally read enough good source code examples to really understand what OOP is about.And thanks to this book I now have concrete examples of TDD that are relevant to my everyday work, and lit up those light bulbs that I can't wait to apply to my own work!
S**E
Changed the Company
The old adage that you recognise what you need when you see it applies here. I only used the chapters on refactoring and writing device drivers in C.I took the provided code concepts and extended them to provide pseudo obect oriented classes in C.We work in R and D with communications algorithms. The challenge is writing extensible comms codecs when the comms channel is not understood.I do not exaggerate when I say that adopting this approach saved the company. We had a hard time when our algorithms were failing in an unexpected way. Once we had field data we were able to change the algorithm without affecting the other code interfaces and produce a new design and test it in hours.I wholeheartedly recommend this book to all embedded coders.
H**S
Reference book for embedded development in C
This books is a lot more comprehensive that the title lets on. Yes, it is mainly about TDD for C code, but the author also discusses good clean and SOLID practices from programming in pure C, which is something not found in many books. The code examples are very well explained, and nothing is ever done without an earlier explanation, which allows one to easily understand everything in this book. Also the philosophy behind test driving your code and how it interacts with agile methodologies is explained well. The only problem I have with this book is that it could be a bit more extensive. The provided examples are all very simple which is good to understand the concept but if you want to use these concepts in real and complex situations you are going to have to figure it out by yourself or find information elswhere. Also, testing in an RTOS environment isnt covered, which is a shame. So overall this is a great book from which I learned a lot, so much so that I hoped it featured more complex examples and use cases.
D**S
N/A
N/A
M**0
A must read
In general a developer focus on development of product itself, this book gives a different perspective, highlighting importance of test strategy in order to develop better code from the beginning. A must read to create awareness.
Trustpilot
4 days ago
3 weeks ago