TDD for Embedded C
2020-02-20 18:20:35 UTC
Most useful learnings:
The process of writing tests before writing code and ensure the test fails before making it pass.
Concepts v exercises:
Presentation v discussion:
I personally would like to learn more about designing a code architecture that facilitates testing, but that may be outside the scope of the training.
Dealing with a lot of legacy code (code without tests). The hurdle to get that code under test requires a lot of buy in from management. Any new projects will certainly use TDD.
Challenges to applying:
Buy in from management and an understanding of how important robust code is
Legacy code workshop:
Recommend to others: