TDD for Embedded C
2020-03-27 21:30:43 UTC
Most useful learnings:
Develop tests one at a time.
Concepts v exercises:
Presentation v discussion:
Less disruptions during presentation (i.e. no need to adjust presenter image size during the presentation, and the smaller version of you is better for me).
More guidance initially on how to do certain things to get over the mental blocks. That guidance could simply be in the form of a quick reference guide for the various types of testing patterns.
So nice to have such a seasoned trainer and someone experienced in the subject. It seemed that no matter what curve ball questions were asked, you had heard them all before and had a great answer which typically included pros and cons about various approaches.
Bring it on!
Maybe. I don't have an IDE setup yet TDD. My normal test development process is simple code editor (scite) and Make and GCC.
Challenges to applying:
Getting common unit testing framework adapters for each code base to use when touching the various projects each week, along with activating CI for them (some CI is already active). There are some using CTest, some using Unity, some using ztest (zephyr os project). My colleagues taking TDD class liked CppUTest and I like the code coverage of it.
Remote deliver worked great for me, as I am work-from-home developer anyway. I usually prefer to travel for training to leave the workplace behind, but keeping the class short (4.5h per day) allowed for catch-up workplace work, but didn't allow for extra time to spend on training class assignments.
Legacy code workshop:
Recommend to others: