Course:
TDD for Embedded C
Date entered:
2021-10-25 10:29:39 UTC
Course rating:
Very Good
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:
Good balance
Presentation v discussion:
Good balance
Course improvements:
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.
Exercise rating:
Excellent
Exercise improvements:
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.
Instructor comments:
Better prepared:
Much better
Start tomorrow:
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".
Other comments:
Legacy code workshop:
No
Recommend to others:
Yes
Quote permission:
Yes