TDD for Embedded C++
2019-12-16 10:35:32 UTC
Most useful learnings:
Thinking of the tests more from a behavioral point of view. So far, I tended to pre-define my APIs and then write tests for each API.
Also, it was useful to see how small the steps can be.
Concepts v exercises:
Presentation v discussion:
I thought the exercises were good, with the instructions to guide along the way. I don't really have any suggestion for improvement.
I can start going in that direction tomorrow, especially for the refactoring side.
Challenges to applying:
Most existing tests are not simple unit test, as we build in most of our software framework. I don't think I want to modify too much the existing tests at this point. But for the next new component I get to write, I will give a "real" unit test a go, and see how it goes.
Legacy code workshop:
Recommend to others: