TDD for Embedded C
2021-10-25 10:29:39 UTC
Most useful learnings:
writing one Test and let it fails and the fix it first, results in less written code/tests than writing a batch of tests and then fix each test.
Concepts v exercises:
Presentation v discussion:
i was familar witch test-frameworks. But for one who does not have seen such frameworks it could be difficult to follow. Maybe for such attendees you should frist show the videos of the homework first and then let doing the exercise.
exercises are good. But Mocking in CppUTest feels like pain ;)
Maybe a Testframework for C for the Embedded TDD C-Course is better. Give Ceedling with Unity chance. It includes also the Fake Function Framework (i have not used it yet) and i find that mocking is a littel bit more better to implement.
because i used it (a bit differently), i have to change only small things to start tdd in its correct way.
Challenges to applying:
legacy code has not often a terrible complex interface. If the interface has to much arguments for the functions they are "untestable".
Legacy code workshop:
Recommend to others: