TDD for Embedded C/C++
2023-03-08 20:28:01 UTC
Most useful learnings:
The process of building up new features in very small steps based on tests.
Concepts v exercises:
Presentation v discussion:
Maybe more of a focus (exercises) on integrating TDD into large legacy code-bases. Many people wouldn't be able to have "Greenfield" scenarios, and I don't think there was an actual exercise that we had to go through to begin testing in a scenario where there was a lot of legacy code already written.
Just as mentioned above, an exercise to add unit testing and begin TDD in a legacy code scenario.
James is enthusiastic and helpful. I also liked his corny programming jokes.
I doubt it. There are many many different modules that our team contributes to, and there are many other people that contribute to those different modules as well. I think our team will have to come up with a strategy to try and implement TDD for our scenario, but it likely will take time to get to that point.
Challenges to applying:
There are many different git repositories that we contribute to, and we are not the owners on many of them. We don't necessarily always have the authority to decide whether unit testing and TDD are options for different repos.
I think James did as good of a job as he could have with the remote delivery. However, I feel like a course like this will always be better served in person.
Legacy code workshop:
Recommend to others: