• Course: TDD for Embedded C++
  • Date entered: 2019-08-30 00:12:48 UTC
  • Course rating: Very Good
  • Most useful learnings: Disciplined approach to unit testing and exposure to two unit test framworks.
  • Concepts v exercises: Good balance
  • Presentation v discussion: Good balance
  • Course improvements:
  • Exercise rating: Very Good
  • Exercise improvements:
  • Instructor comments: Knowledgeable, personable, humble.
  • Better prepared: Much better
  • Start tomorrow: I'm not a C++ programmer, but I will look into Python and Bash unit test frameworks.
  • Challenges to applying: Haven't figured out how to apply unit tests in a functional programming environment, when function calls are more than 3 deep.
  • Other comments: While doing exercises partners or the mob, speed was achieved by making things match up and so that they compile, and thought about the what the tests do and how they should be written were lost a little bit. The attitude was kinds of like reading Stack Overflow: How do I get past this immediate hurdle, not how do I solve this problem for good. Getting over the hurdle is find when introducing the unit test framework into legacy code and getting the first test to run. But after that, students should give more thought into what the tests actually do and how the mocks work, rather than matching up function call parameters by order and type.
  • Legacy code workshop: Yes
  • Recommend to others: Yes
  • Quote permission: Yes