TDD for Embedded C
2021-05-27 16:29:59 UTC
Most useful learnings:
Do and fix one thing at the time.
Concepts v exercises:
Not enough exercises
Presentation v discussion:
Too much discussion
Sometimes, the discussions are too long, the discussion can be closed as soon as the answer has been given.
2)The tests names rarely have good names. Is there a coding standard for test naming ?
For the 3rd day, it was difficult for me to understand what is the purpose of each file (even knowing the use of mocks). So, no idea where to write what.
A simple header in each file to explain the purpose of each file can be useful.
Easy to understand even for french speaking people.
James helps the course to be nice and interresting.
No, need some more training and exercices to be efficient. But I will use it soon.
Challenges to applying:
nothing seems to prevent applying TDD. That's great.
Only mock requires to add tools in the setup.
I appreciate that the course is really well prepared (tools, videos, gather.town, cyber dojo).
Legacy code workshop:
Recommend to others: