TDD for Embedded C
2020-05-01 03:49:10 UTC
Most useful learnings:
The overall process of TDD with practice writing and doing tests. Having feedback on that practice.
Concepts v exercises:
Not enough exercises
Presentation v discussion:
Too much presentation
Doing a bit more with the exercises such as setting up the mocks, fakes, and spies. Having to set them up would be useful practice.
While I think I understand when mocks vs fakes/spies would be useful, having more examples of mixing both to show the difference would be useful.
Setting up mocks, fakes, and spies as students in an exercise or students doing it at the same time as they are being demonstrated. More interaction with them would be useful.
More individual feedback on how our tests are structured or if we are doing too much or too little in the incremental testing.
Challenges to applying:
Some of the videos that were recordings of classroom lectures have sections that were answering questions at a whiteboard that were unable to be seen in the video. I think redoing those videos for web-delivery would be useful and the lecture could be shortened since you can assume students will ask for clarification later if needed like they were doing in the recording.
Some of the lecture portions could be done in videos giving more time to expand the exercises, such as to building the fakes, spy, and mocks.
Legacy code workshop:
Recommend to others: