TDD for Embedded C
2015-11-02 03:25:05 UTC
Most useful learnings:
Test legacy code using test doubles, spy and mock etc to simulate.
Concepts v exercises:
Presentation v discussion:
Spent too much time talking about the survey in the first day, if we need to do it, I think they should be done at the end of the training. It is too early to talk about the survey questions before we fully understand what the training is all about.
I think the exercises are excellent.
I think talking about the survey, the first impression of concern and surprise etc wasted too much time on the first day.
The testing ideas can be applied more easily, e.g. using more simulation in embedded testing.
Challenges to applying:
It takes much more time to do TDD than DLP for most features that are not too complicated like circular buffer, I don't think boss will appreciate it at all.
Explain what TDD is, how it is done, the exercises are great, but don't try too hard to convince us, especially don't try it on the first day. The exercises are course material speaks for themselves.
Legacy code workshop:
Recommend to others: