• Course: TDD for Embedded C
  • Date entered: 2015-03-27 10:56:13 UTC
  • Course rating: Good
  • Most useful learnings: What problems TDD solves, build process(make and such), cygwin, how to test legacy code, solving compilation and linking problems.
  • Concepts v exercises: Not enough exercises
  • Presentation v discussion: Good balance
  • Course improvements: More exercises. How to store the tests (version management) in order for anybody to be able to run the tests. I would like a list of frameworks suitable for TDD. (Cpputest is one of these. What others ?) I would like at least 1 exercise about refactoring code.
  • Exercise rating: Excellent
  • Exercise improvements:
  • Instructor comments: He is ok. Suggestion: during presentation pick one person randomly and ask how they feel about the concept explained: eg: "Victor what do you work on after the training ? How would you use this concept applied to you ?"
  • Better prepared: Bring it on!
  • Start tomorrow: For my team TDD is not directly applicable (I don't do unit/ module test). Concepts and techniques I can apply: test from interface level points, build an ok interface in the code in order to have a replaceable module(unit of test).
  • Challenges to applying: Making the boss understand that tests first or during coding must be planned as soon as a new feature starts being implemented.
  • Other comments: All was ok.
  • Legacy code workshop: Yes
  • Recommend to others: Yes
  • Quote permission: Yes