TDD for Embedded C
2020-03-13 20:00:54 UTC
Most useful learnings:
- While doing the exercises, I noticed that changing and refactoring code was not scary any more.
- Try to eliminate the habit of debugging.
- How to test hardware.
- Some solutions are dirty when working with legacy code. But it's necessary.
- How to start writing test to your system was challenging. I think ZOMBIE rule is going to solve it.
Concepts v exercises:
Not enough exercises
Presentation v discussion:
- Adding an example for working with legacy code would be great. (I know that is challenging)
- We have been introduced to concepts like test doubles, mocks, fakes, spy , null object ...etc.
Adding one or two examples of these concepts would be helpful. It does not have to be 1 hour exercise. it can be quick exercise. Or James does an example of one or two of these concept.
- The last hour of the first day in the course was not the most interesting. I don't remember now what we were talking about.
- In the second day you talked about the importance of testing. I think that talk is great and the idea could be delivered in shorter time. You could use the remaining time to explain something else.
The exercises were good. If I have some comments I will email it to you.
Bring it on!
After my organization agreed, I would apply it for new written code.
Legacy code would need time.
Challenges to applying:
- Convincing the organization and the team.
- For embedded system we would need Continuous Integration tool setup. It would need time to be comfortable with the pipeline of writing code in the testing environment until the code is in the hardware.
Legacy code workshop:
Recommend to others: