TDD for Embedded C
2016-10-06 10:27:59 UTC
Most useful learnings:
How to do TDD all way through by taking small steps and only making one simple change at a time.
Concepts v exercises:
Presentation v discussion:
Maybe by including some real life examples on TDD where it has been used in a larger project.
It would have been nice with an example for the following cases:
* legacy code example - add and/or change a feature in a legacy system.
* Include a bit more architectural decisions. I.e. start with a problem, then suggest a solution and then TDD the suggested solution. This is especially to make it clear whether the TDD approach effects the architecture in a certain way.
Yes, I think it is important to start right away to get the most benefits. I may need to start out with getting some tests into a legacy project, but I will also try to continue with some toy examples to get more used to the approach.
Challenges to applying:
Legacy code is probably the biggest challenge, but I believe the appropriate tools have been provided to handle this case, but I still need to try it out myself.
For a remotely delivered course, I think it was very well organized and provided everything I could have expected. There is of course a limitation in not working with your own code, but given the duration of the course I think this is acceptable.
Legacy code workshop:
Recommend to others: