TDD for Embedded C
2017-03-02 08:57:06 UTC
Most useful learnings:
Cppumock looks to be a very useful framework for what we need.
I enjoyed the exercises and the chance to write C after nearly 20 years away from it :)
(I came into the course with lots of automated test/mocking experience and some slight TDD. But attended alongside my 3 colleagues to help etc).
Concepts v exercises:
Not enough exercises
Presentation v discussion:
If you plan to skip slides, don't have them (they can become notes in slides for attendees if you think they have use)
More exercises (see below)
The exercises were the best bit of the course. However I felt that day one would have worked better with some tiny exercises to illustrate the cycles of TDD better.
Something like "min of a series of numbers". Similarly a tiny small mocking example to start day 3.
I felt at various times that you are under-prepared. Day three afternoon was an example of this - the walk through of your RTOS and legacy were poor. You looked surprised too many times and without concrete examples (exercises) it felt little more than being shown the results of a google search.
The other example was the question board. I felt that in you afternoon you could have looked at the questions and then come along in the morning ready to give stronger and shorter answers to each questions.
Challenges to applying:
Finding the right work to get early wins.
TDD also fits in well with our functional safety work where we must get 100% code coverage.
Remote is fine. It was our fault that we didn't all have headsets which would have helped.
Legacy code workshop:
Recommend to others:
Only if improved