TDD for Embedded C
2015-11-13 13:22:05 UTC
Most useful learnings:
1. To start, just "write a test"!
2. Don't write any code unless its to fix a failing test
Concepts v exercises:
Presentation v discussion:
I thought the balance between theory, background and the exercises was just right. Can't think of anything to be changed.
I thought they provided a good introduction to the problem space. I liked the use of the Cyber-dojo to provide a pre-tested build/execution environment and multi-person working.
Very good, patient and willing to discuss 'the why' and well as 'the how'. Obviously understands the problems and the solutions, and where to go look if he doesn't.
We're currently in a 'definition' phase (requirements capture and review), but this will generate work-packages for implementation. The intention will be to use TDD to develop the code and tests for these packages as a learning exercise, then integrate into our Jenkins regression environment.
Challenges to applying:
Getting buy-in from other members of the team that haven't received the training.
Integrating it into our development process and understanding impact on 'velocity'
Estimating how long it will take for others to understand and use TDD effectively, and mitigating against management expectation on team velocity.
Legacy code workshop:
Recommend to others: