TDD for Embedded C
2021-07-16 17:10:44 UTC
Most useful learnings:
The most useful concepts for TDD Off target unit testing for new code, new tests was to develop a test (to fail initially), then develop the prod. code to get it to pass, incrementally and together, so that you can build off of each subsequent effort, refactoring as needed as you go.
Concepts v exercises:
Presentation v discussion:
I believe in Day 2 videos it helped to show where in the test effort TDD units testing resides. Perhaps show that up front in Day 1, to give folks an initial overview of TDD unit testing, to other testing that happens independently and later on. (integration, more pa/qa product testing)
Knowledgeable, likeable, and a decent mix of varied experience with trying to keep the current thread or concept being delivered and reinforced via example, and run time training of those live.
Perhaps. Trying to decide if cpputest is the right fit for both off target, on target and if so, wether to use Visual Studio, Cygwin (windows), or Linux environments as the test platforms.
Challenges to applying:
the above first. need to look and see as well if cpputest on target is something we should entertain or not. possible size constraints, but additionally maybe the bang for the buck switches more to integration tasks on target anyways.
Legacy code workshop:
Recommend to others: