TDD for Embedded C
2015-06-04 00:55:04 UTC
Most useful learnings:
How to write tests without modification of the production SW and without being on the target HW.
Concepts v exercises:
Presentation v discussion:
In my previous lifetime, I was an Avionics Systems Engineer where I read code & made minor SW updates, but didn't do significant coding. In my new current role, I am a Systems and Software engineer with the expectation that I will become more involved with SW over time.
I am giving you all of that background so I can say that I thought the exercises were great. The exercises were able to be accomplished with minimal coding background which allowed someone like myself without significant coding experience to understand and appreciate TDD.
Great. I enjoyed the class.
I think as a company we should look to pursue it. However, since we are a medical (highly regulated) company, we would need to setup process' to support this type of development. So I don't think it will be "tomorrow", but I hope we can in the near future.
Challenges to applying:
In highly regulated environments, where minimal code change is usually desired because changes require regression analysis, re-execution of Validation/Verification activities, structural coverage analysis, etc. it may be a challenge to "train" management on the advantages.
Legacy code workshop:
Recommend to others: