TDD for Embedded C
2016-03-24 21:07:09 UTC
Most useful learnings:
Resist the desire to write code that does not have tests for it yet. It will help you develop a more useful API for your code.
Concepts v exercises:
Presentation v discussion:
It may be helpful to have the group talk about the tests that they should develop before they write the tests themselves. In some cases the tests were outlined in the instructions but when they weren't it took me a while to decided what to test.
Very knowledgable on TDD and able to describe the benefits. The experience definitely shows as he was able to provide examples of problems companies have had in the past.
I think the start up cost is too expensive until I am better at writing tests and using this methodology. For now I will use it in my personal projects and online courses until I am proficient enough to introduce it into my work.
Challenges to applying:
Convincing everyone else. The portion of the codebase I touch is not very large. So many other developers aren't using TDD so it will be difficult to convince them all. All I can do is use TDD for myself and hope they see the benefits.
Legacy code workshop:
Recommend to others: