TDD for Embedded C
2018-10-13 08:46:48 UTC
Most useful learnings:
When changes need to be done, ALWAYS keeping the code functionally working.
Concepts v exercises:
Presentation v discussion:
I think it is really good already. Maybe check the customer's development tooling and see if the test stuff can already be included in it. For example extend an existing customer-eclipse project with cpputest project / build target. Maybe hint at a way this can be included in the customer's design flow.
The online dojo platform is already a nice and clear tool for group exercises.
Very knowledgeable and explaining things in a clear way.
Bring it on!
Yes, in fact I am in the middle of starting a new company and the missing 'part' in software development flow is testability / coverage part. I feel that we can manage this using TDD (in combination with Gerrit).
Challenges to applying:
None really (that I can think of now, so shortly after training). Maybe in the beginning it will bring a little extra overhead in the form of time to do the initial setup / find the best way to fit it into the workflow.
I went in a bit skeptic since I have seen test driven development fail at a company I worked for before but I am convinced that this is the way to go. Reason for failure back then (I think) was that it was almost like swearing when you would want to bring in concepts such as object oriented design or abstraction to embedded software development.
Legacy code workshop:
Recommend to others: