TDD for Embedded C++
2016-10-31 14:36:41 UTC
Most useful learnings:
Adding tests beforehand is not an overhead. On one hand, it prevents degrades. On the other hands, it challenges us about the required behaviors before we delve into the actual implementation.
Concepts v exercises:
Presentation v discussion:
I've completed the unfinished exercises. I'm setting up the build environment. I will convey what I learned to my team.
Challenges to applying:
Concept change - requirements and software can be evolved in a spiral way, thus the approach (tests and implementations) with which we achieve them. At my workplace, sometimes we wait for requirement clarifications without starting from known points (thus a time loss). Other times we did the implementations too much without re-considering if the implemented behaviors match the requirements, or they can cover reasonable error cases.
If the next question - "legacy code workshop" means "using Mock for legacy codes", the answer is Yes. Otherwise, the answer is No.
Legacy code workshop:
Recommend to others: