TDD for Embedded C
2018-10-12 11:19:05 UTC
Most useful learnings:
The mindset that is needed when changing your strategy towards TDD. It's really not just about creating unit tests, but developing your code with testing in mind.
Concepts v exercises:
Presentation v discussion:
The parts where we would have discussions or exercises on our own code, as of Wednesday, were a bit messy. It felt that a better preparation and structure would have created better results.
See previous comment.
James is a good instructor, who knows what he's talking about. He calmly explains the different topics and listens actively to questions asked.
I probably need to take some time to revisit some concepts to gain better knowledge. I also need to understand all/more possibilities of CppUtest.
Challenges to applying:
Time to get started. Initially it will take more time to do unit testing, because I'm not experienced in it yet.
I really liked the subject of unit testing in general and for embedded. I think the training at least kickstarted a healthy discussion on what to do within this company and I even think the outcome will be that unit tests will be used in the future.
Legacy code workshop:
Recommend to others: