TDD for Embedded C
2017-05-10 08:08:39 UTC
Most useful learnings:
I think it was the whole concept of using such workflow for the development. Previously I was aware of some details about TDD, but while trying the ways if TDD now, everything was new.
Concepts v exercises:
Presentation v discussion:
There were some issues with the dojo-box in web used for programming. The commits went sometimes out of sync after TEST button click -> no diff was added to the actual code (while still being visible in the diff view).
Yes, because we use similar unit-test framework to CppUTEST. We definitely do not follow the TDD development concept I learned during the training days now, but all the tools exists for that and i would not have any problems to continue this in my office. I still might need some tries to get more used to it - using the tests and TDD (as we learned during the practice) with such small steps was a challenge. But then again trying different things is essential.
Challenges to applying:
Probably just the time. As mentioned, we have the tools already, but we are not using these in such way - during the sprint plannings, nobody is not considering the units tests being the part of the actual implementation, rather it is considered as separate subtask, which is carried out before or after the implementation. So the team might not consider these differences, when for example sizes are estimated.
Legacy code workshop:
Recommend to others: