TDD for Embedded C
2020-03-26 20:12:21 UTC
Most useful learnings:
The TDD process. Before this course, I had experience with writing tests, mocks, stubs, code coverage, and other technicalities. This test was extremely valuable in emphasizing HOW to implement the process of writing tests to drive your programming.
Concepts v exercises:
Presentation v discussion:
I think by having an exercise on refactoring legacy code via TDD, or on adding tests to legacy code.
I think the exercises were quite good. I would like one additional exercise where we are given completed code, But there are no tests and our job is to add tests. One of the things I have not experienced from this course is taking existing code and adding tests to it. We highlighted this in the slides on day 3.
Very personable and easy to interact with. Good job!
I plan to start this afternoon! I'd like to try using TDD with a new feature I must add into my code this sprint.
Challenges to applying:
I think the hardest thing getting going is adding tests to existing code that has many dependencies. When we've begun adding tests in the past, we were turned away because of all the dependencies that must be either mocked, stubbed, or cleaned up. This initial time sink is a big challenge, but one that I think would be worthwhile to solve. I hope to take on this role of pushing our team to begin resolving these dependencies, so that our code has tests.
I think the remote delivery was effective. We also have no other choice these days! :)
Legacy code workshop:
Recommend to others: