TDD for Embedded C++
2018-03-15 19:51:54 UTC
Most useful learnings:
The test harness. Adding another tool to the arsenal.
Concepts v exercises:
Not enough exercises
Presentation v discussion:
Too much presentation
I learn by hands on experience. The more I'm able to do something and succeed at doing it, the more I'm able to truly evaluate the worth of the idea/concept. I felt that too much time was spent "advertising" why TDD is good through slides. I recognize that the class isn't that long... there is a lot of material to be covered.
It might be nice to have the students build an application from ground up the TDD way.. Something very simple to comprehend the logic of what's going on so that the student can more fully focus on writing the tests and learning the test harness. Remember, this may be the first time that a test harness is being seen. I felt that the second exercise required too much pre-understanding of the initial code. It wasn't overly complex, but it was complex enough that more attention was spent trying to understand the code instead of understanding/writing the tests.
Yes. I learned good skills in this course. When I'm writing code or improving it, I'll start looking for ways to utilize TDD.
Challenges to applying:
Getting it started. Jaguar doesn't have Unit Tests. Epoch does. It's easy to write the tests in Epoch, but things would need to be setup server side first for Jaguar.
I like the ambiguity of the "animals".
Legacy code workshop:
Recommend to others: