Course: TDD for Embedded C

Date entered: 2016-04-18 15:46:29 UTC

Course rating: Excellent

Most useful learnings: I actually liked a lot the idea of being able to test code in a few milliseconds. It means that ideally in every file-save I could know if I broke something with the few lines-changes I've just done. Also, and as pointed out, having meaningful names of the test-cases help a lot understanding what is broken.

Concepts v exercises: Good balance

Presentation v discussion: Good balance

Course improvements: The only change I would do, would be a 1h walk-through the FFF and CPPUTEST available commands before moving to the adaptation of the corporate code.

Exercise rating: Excellent

Exercise improvements:

Instructor comments:

Better prepared: Much better

Start tomorrow: I feel trained to do so. But as a big project, it will only be effective if I managed to make my colleagues to start doing it too... (this would be a too big challenge for one person). I think I'm in a good position to convince them now :)

Challenges to applying: Not sure that we are going to be allowed to refactor to interfaces-implementation in order to proper unit-test the code. However, the training given taught us to "engineering-techniques" (see I was listening) to overcome some of the problems.

Other comments: It was a very nice training. I'm glad I had it. Thank you James!!

Legacy code workshop: Yes

Recommend to others: Yes

Quote permission: Yes