Course:
TDD for Embedded C/C++
Date entered:
2025-05-07 18:46:07 UTC
Course rating:
Excellent
Most useful learnings:
Value of unit testing; and test before you code; and test and code at the same time.
Concepts v exercises:
Good balance
Presentation v discussion:
Good balance
Course improvements:
On Day 1, it's natural for newcomers to have doubts about applying TDD to their existing legacy codebases. Instead of dismissing these concerns, it might help to proactively acknowledge them with a message like:
"It's okay to have questions—try TDD hands-on during this workshop first, and by Day 2 or 3, we'll dive into how it fits with legacy systems."
This kind of framing could foster more open-minded and engaged participation right from the start.
Exercise rating:
Excellent
Exercise improvements:
something to consider...
The 3rd day exercise was non-intuitive and took a while for me to understand. Then I had to explain it to my test partner as well.
I know you explained it all well; but it was unfortunately not enough.
Is there a way to make it easier to understand?
e.g. one slide- which shows the relationship.
"IPRW_CpuUMock.cpp" --> to mock IO Read/write functionality; and it will be used by FlashTest.c, to help test/develop Flash.c
" IPRW_CpuUMockTest.cpp" -> is JUST for testing " MockFeatureX" -- and can be used as a reference while developing FlashTest.c
Instructor comments:
I loved the subtle(ish) sense of humor. I am impressed and delighted with your sharing of the material and even the website access - in case we want others in our team to try out TDD! This is very generous- thank you.
Better prepared:
Moderately
Start tomorrow:
Perhaps.
I need to identify a small task where I can write/add unit test - which is low-risk; and perhaps not too many dependencies on the existing legacy code.
Challenges to applying:
We have test framework and unit test and integration tests and automated CI - etc everything in place- so that's not the problem. So there may not be any real challenges except finding a task and start applying the ideas.
Other comments:
The remote delivery / website is really powerful!
It is not as intuitive as one might think - but that could be me: I took a while to adapt: e.g. finding where to enable/disable screen share, where to set background, how to even change my name etc -- but then , I had missed the prep work :)
Legacy code workshop:
No
Recommend to others:
Yes
Quote permission:
No