TDD for Embedded C
2018-09-04 14:23:04 UTC
Most useful learnings:
The TDD workflow of writing just enough code to fail and pass a test before jumping too much into implementation.
Concepts v exercises:
Presentation v discussion:
I think this course may have been a bit more tailored to Blue's purposes. With that in mind, I think that last two days of the training were a bit unnecessary for some in the class. Going through our code and trying to tie TDD in after that fact was not very helpful; it felt more like cleaning up our test cases than following TDD.
I think the exercises got the point across. There was some confusion about the instructions on some of the exercises. I think it would be nice to have clear instructions in one place than in comments in multiple places. It would also be nice to have some hints along the way; there were times we had to guess what was needed. I think Code Dojo was a great tool to use, but I wish the editor used more real-estate on the screen... in the day of widescreen, high resolution monitors, there's no need to limit ourselves to a small square work area.
James was a great instructor: very respectful, entertaining, and clearly knowledgeable in the area of TDD. He did a great job answering our questions and helping us understand the material.
Nope... schedule it too tight and I don't have the time to figure out how to get CppUTest integrated into my environment (I was hoping there would have been some help with this during training, but I misunderstood what TDD was).
Challenges to applying:
"Write a little, test a little" still seems to be a more comfortable solution to development. I'm not totally convince that TDD is the best approach. I have to start writing code to design it; TDD relies more on a developers abilities to design code before implementing it... I'm not that good.
Legacy code workshop:
Recommend to others: