TDD for Embedded C++
2016-11-18 22:46:05 UTC
Most useful learnings:
building code in parallel with the tests. Simple concept but never occurred to me.
Concepts v exercises:
Presentation v discussion:
The class could be improved by adding some material that would help adopters facilitate the maintainability. Suggested turn-key templates that helps how to keep the tests up to date with code changes. Mechanisms to ensure test harness is run with small incremental changes.
Anything that avoids having to rely on developer discipline.
the prepared circular buffer was good.
I suggest having a prepared legacy example. Working in our own code is a good idea however it was lengthy.
Adding an example that would allow developer learn how to restructure a legacy into a more testable would be greatly beneficial.
Thanks James, enjoyed and learned new skills that I intend on using.
Yes, however I would only tackle a small scope features.
Challenges to applying:
In an organization as Panasonic it's not uncommon for one group to have little understanding or what the other groups are doing. I can see that code changes might require other groups involvement for stubbing and test case definition. How to get other group resource support could be challenging.
You can quote me but I ask that you leave out my employers name.
Legacy code workshop:
Recommend to others: