TDD for Embedded C++
2019-02-08 22:13:03 UTC
Most useful learnings:
Only develop what is needed at the moment / when it is needed, enough to allow tests to be written and executed.
Concepts v exercises:
Presentation v discussion:
For the 2-day version we had, I would have liked a little more trade coverage of Mocks, as they appeared to be very useful for our type of embedded development. It is always a balancing act to limit off-topic or marginally-related discussions, which did steal some time away, but no fault of the instructor since the topics were typically started by others.
I would have liked to cover, or at least review, more complex test sequences, maybe where several small tests build on each other, supplying preconditions to later tests. I realized this would be difficult in the 2-day version, but perhaps being provided a more complex set that we had to modify or "fix" as the exercise.
Very personable. Spoke well/very understandable. Did not "talk down" to those less familiar with some of the capabilities of newer C++ standards/versions. Very good use of online tools to monitor, help, and share during exercises. Was flexible and adaptable to needs/requests of audience.
A definite maybe! ;-) My "tomorrow" won't really be until next week because of other training on other topics that consumed the rest of this week after the TDD training. I will be reviewing how myself and the other developer on my current project could begin to incorporate some of this. As mentioned in another response, I believe this is where having learned more about Mocks (development and use) could have allowed more immediate and broader application.
Challenges to applying:
Requires refactoring and development (simulation/Mocks/etc.) to enable test execution on a PC.
Legacy code workshop:
Recommend to others: