TDD for Embedded C++
2018-02-01 00:37:22 UTC
Most useful learnings:
Going through the circular buffer and light controller exercises to learn how not to code too much in advance beyond the test.
I got a lot out of the flash driver exercise, learning how mocks could be useful to allow me to get testing done up front. I've done flash drivers before and testing/debugging after writing the code was very painful
Concepts v exercises:
Presentation v discussion:
Yes on new code.
I see the benefit for starting on legacy code with careful refactoring. I'm more reluctant starting immediately on legacy code until I've practiced TTD with new code first.
Challenges to applying:
A lot of my work is Software engineering, but I don't write C/C++ code daily much anymore. I'm heavily involved on the our OS build, Linux configurations, third-party libraries. There are lots of dependencies, and upstream changes and patches to manage. I don't think this really fits into unit testing -- more integration level.
One technique I try to apply is make small changes rather that batch changes before building and test.
Legacy code workshop:
Recommend to others: