TDD for Embedded C
2016-03-24 21:07:51 UTC
Most useful learnings:
The exercises proved the best way to really understand the cadence of TDD.
Concepts v exercises:
Presentation v discussion:
More techniques/discussions on working with legacy code. It is what we have to deal with 99% of the time.
We could use a bit more time to read over the instructions before starting writing the tests.
I could not start tomorrow because it would take a team decision to decide on which test harness to use and how to integrate to the build framework (which is rather complex)
Challenges to applying:
Need to convince my scrum team (about 10 people). Need to also devise a plan for how to combine unit tests and our QA automated integration tests.
Legacy code workshop:
Recommend to others: