TDD for Embedded C
2016-05-13 11:07:59 UTC
Most useful learnings:
Incremental development and continuous integration with testing done in an agile methodology yields software with less defects.
Concepts v exercises:
Presentation v discussion:
Given a fixed amount of 1 weeks time, I suppose the initial TDD ideology build up may take a little less time like 1/2 a day and start with more exercises to better illustrate the TDD concepts of CPPUTest. The exercises them self illustrate how effective TDD development can be. Just my thoughts.
Little higher number of exercises.
Very well organized training material. Good exercises chosen starting with the simple ones first and building up the contents to use more sophisticated techniques. Handled the timing of answers to some of our nasty questions very well.
Yes. Exercises though only a few helped get hands on to the TDD techniques. Day4 legacy code exercise gave insight into how we can apply them with a fair amount of progress. Not an expert yet but sure I can get there with some practice.
Challenges to applying:
Complexity of our current code.
Legacy code workshop:
Recommend to others: