TDD for Embedded C
2018-03-01 21:07:11 UTC
Most useful learnings:
Techniques to begin a more formal TDD environment versus personal testing which tends to fall by the wayside once the code is integrated into the product.
Concepts v exercises:
Presentation v discussion:
As a smoker, I wouldn't mind a few extra breaks...
Better variable names :^D
Tomorrow? Maybe. I think we'll need to sync up the team (maybe in a week or two when we have our next Dev team sync). Personally, I'm interested in doing this with Xcode's XCTest APIs because it's conveniently integrated with Xcode.
Challenges to applying:
I think Carbon Black is very open to these ideas.
Very good. About the only issue is when everybody is muted and you ask a question, it becomes quiet because we're all muted and have to go out of our way to unmute. I don't know if it would be good to suddenly unmute everybody without warning...
"Why would you want to do TDD?"
Legacy code workshop:
Recommend to others: