Course code: CSR-2
  • Years with company: 1
  • Years programming: 20
  • Primary programming language: C
  • Other programming languages: C++, Python, Java, Perl
  • Unit test harnesses: Unity
  • Something else: I started work in the games industry and have gradually moved into a more embedded environment.
  • Test practice now: Unity for new modules; "system test" for existing functionality; lots of manual testing when fixing bugs.
  • Target system: Bluetooth Audio Chip (CSR)
  • Dev tools: xIDE, shell scripts, make, in-house utilites
  • Build time: 1-5 minutes
  • Coding standard: It's vague
  • Function too long: Too many indented braces
  • Code reviews: Slow & cumbersome
  • Code time: 10
  • Test time: 50
  • Debug time: 40
  • Favorite thing about dev: When it works at the end.
  • Least favorite thing about dev: Spending a long time debugging a problem and finding it is a one-line fix that should have been picked up earlier.
  • Tdd knowledge: I have read your book and used Unity as part of developing a new feature in our product.
  • Why are you attending: I have had a taste of TDD but I want to learn more, especially how it could be used with legacy code. It is also being arranged for our whole group so I am attending as part of that.
  • Back