TDD for Embedded C
2017-10-02 13:49:50 UTC
Most useful learnings:
how to use CPPUTest. I had never heard of it, so seeing it used was interesting. I would have liked more information on it (additional test APIs, maybe see it get compiled/installed from scratch)
Concepts v exercises:
Presentation v discussion:
I liked the flash driver example. I would like more like that. The light example was only okay, because it wasn't as well defined. The state machines for the flash driver really helped explain TDD better, and showed natural areas for tests to be written. that wasn't as obvious for the lighting example. Maybe swap the two around in future classes.
As mentioned above, I would like to see CPPUTest installed from scratch, then do the Flash driver first, then the lighting example. The flash driver seemed like it was defined better, so it was more obvious on the tests that needed to be written.
Good balance of real world examples and theory.
I'll try some easy stuff. After existing fires are put out first. I would like to show my co-workers what it means to do TDD and show them how it can save time, but I think it will be an uphill battle for my boss.
Challenges to applying:
Boss loves waterfall, and he thinks testing should wait until the end when the product is feature complete.
I never received the preparation email, so I felt I was behind before I started.
Legacy code workshop:
Recommend to others: