TDD for Embedded C
2021-09-03 19:33:15 UTC
Most useful learnings:
Process for achieving full test coverage while also reducing workload
Concepts v exercises:
Presentation v discussion:
By having more of it.
The last exercise with the flash-programming had several steps that were plain repetition of the previous steps.
You add a test for checking an error-bit in the status-reply.
Then you do the same thing, but with a different error-bit.
Then you do the exact same thing again, but with yet another error-bit.
I think it would have been enough with a single error-bit check.
Or perhaps some variation on the specified behavior of the flash-programming-module when it detects the different types of errors.
No. Because its weekend and I intend to drink beer and watch the football instead of working.
Challenges to applying:
Some are already able to deliver "perfect" code.
If your code is "flawless", then of course you dont need to spend a lot of time on testing it.
There are no know bugs, so you dont need to spend a lot of time on debugging it.
You see the firefighters? cant be related to your code since that code is "flawless". ignore them and focus on your next task instead.
So if you are already spending most of your time on writing code and almost none of their time on doing tests and debugging.
Then TDD would just seem like additional workload.
Legacy code workshop:
Recommend to others: