TDD for Embedded C++
2021-04-19 21:23:26 UTC
Most useful learnings:
The importance of writing testable code.
Concepts v exercises:
Presentation v discussion:
1. Request more participation from the audience by asking more questions.
2. Explain test doubles in more details. I still don't know the difference between a stub and a fake.
3. Explain exploding fakes technique in more details (and what it achieves). Add explanation video or link as homework before the workshop.
1. It was very hard to focus on the exercise implementation with a parallel discussion. Maybe ask attendees to post a message on the chat when they need help, and break out the room to a separate call to speak to the ateendee alone?
2. Post comments/observations about the exercise resolution directly to the developer on the attendee webpage. And maybe only highlight the most meaningful to the team before the course starts.
2. Publish complete exercise solutions on the website (source code on top of video)
3. Make exercise instructions clearer. Embed them or add a link in the cyber dojo space. Or post full textual instructions in test class source code as comments. I recall not knowing what to test in the mock example.
4. Sort the exercise files by alphabet on Cyber Dojo. If a source code file should not be modified by the attendee, then set a lock (or a comment)?
Bring it on!
I'm on it :)
Challenges to applying:
Management puts a LOT of pressure on feature development. It was embedded into our developers, they struggle switching to this new TDD mode...
Legacy code workshop:
Recommend to others: