TDD for Embedded C++
2018-11-29 21:11:25 UTC
Most useful learnings:
The primary benefit for me was learning CppUMock. I have experience with Google Test, so transitioning to CppUTest was not too difficult, but I hadn't done anything with CppUMock yet.
Also, the course helped remind me to focus my tests. I have written some "rambling" tests.
Concepts v exercises:
Presentation v discussion:
A remote course is difficult simply due to logistics, but I thought everything went very well.
I don't know that much can be improved. I enjoyed the exercises quite a bit.
James did an excellent job leading the instruction and guiding everyone through the exercises.
Bring it on!
Yes. CppUTest was just incorporated into the product line I'm working on. And, I'm the first to write unit tests for several classes that I recently created. They are being written after the fact, but the classes were written to support testing since I had been doing that for several years before coming to this company.
Challenges to applying:
The primary challenge is legacy code where kernel functionality is not isolated; it is intertwined throughout the code. The secondary challenge is the aversion to "refactoring" several engineers have expressed.
Legacy code workshop:
Recommend to others: