TDD for Embedded C
2018-09-06 18:14:29 UTC
Most useful learnings:
The importance of the TDD cycle, and the importance of an easy-to-use framework. I see myself switching from cmocka to CppUtest based on this.
Concepts v exercises:
Presentation v discussion:
if there were a way to bypass code dojo and just do git push/pulls from my own ide, i'd have a much easier time!
i can't fault the exercises at all! the IDE leaves something to be desired but it was still functional enough.
this is the first "embedded" workshop ive been to that didnt involve a dev board, and I find it funny and that this did not even occur to me until writing this feedback. I mean this in the best way possible, as i never had a sense that I needed a dev board, and my usual 'embedded development' concerns were satisfied - minimizing DOH really is the way to go!
yep - we already use these, or similar, approaches, and have sold management on the value of test driven development
Challenges to applying:
we already use most of the ideas presented - but, It's hard to make test framework changes during the middle of a project
id prefer some more breaks, even if it meant a longer course. I am very far from my nearest coffee source!
Legacy code workshop:
Recommend to others: