TDD for Embedded C
2019-06-10 20:58:56 UTC
Most useful learnings:
How to mimic the hardware (or could be other events in our system like timers or state transitions) to unit test our modules
Concepts v exercises:
Presentation v discussion:
Maybe go over a real example program up front the first day (just presentation and not do it yourself)... although the circular list was simple enough...
Sometimes I got lost at the start of an exercise since I didn't understand the requirements well enough (and went off on a wrong direction - like starting to write duplicate code to what might already be there). My mind is slowing down (getting old (: ) and trying to see the whole picture and directions up front might take me longer than it used to...
Know's his stuff!
Yes, but would need to make sure we can setup (though Michael has already setup himself and me too, for doing examples out of the book)...
Challenges to applying:
We have a meeting with staff (soon) where we need to discuss with Management. One comment during our staff meeting was to make sure it didn't disrupt or cause issues for any of the standards or certification we have or may need to do. We also would need to add a new section under Test within our Software Development plan.
Remote was ok.
I plan to go over the last example (posted results) to make sure I learn from it (since had disruption during the last one).
Legacy code workshop:
Recommend to others: