Course code: BARR-10
  • Years with company: 3
  • Years programming: 12
  • Primary programming language: c
  • Other programming languages: c++, python
  • Unit test harnesses: vectorcast, gtest, cmocka
  • Something else: I like to cook and garden.
  • Test practice now: desktop tests, unit tests, hardware in the loop, software in the loop and system level verification
  • Target system: Battery powered device with radios
  • Dev tools: IAR, gcc, cmake
  • Build time: 1-5 minutes
  • Coding standard: Derived from MISRA along with other best practices
  • Function too long: If its doing more than one task, if you can't see everything without scrolling
  • Code reviews: We require 2 people to approve a Git pull request. We also do more formal design reviews based on risk/safety
  • Code time: 60
  • Test time: 20
  • Debug time: 20
  • Favorite thing about dev: Solving challenges
  • Least favorite thing about dev: Trying to give estimates for how long something will take.
  • Tdd knowledge: Allows you to refactor code and be confident it still works. Easier to find problems quicker.
  • Why are you attending: One of the things I am struggling with TDD is at what level within the hardware drivers should unit testing stop and just be stubbed for other tests to work.
  • Back