Course code: BARR-5
  • Years with company: 2.5
  • Years programming: 4.5
  • Primary programming language: C
  • Other programming languages: C++, C#
  • Unit test harnesses: CPPUTest
  • Something else: A lot of embedded software. Trying to pull CPPUTest into our development. Pushing for more C++. A little bit of embedded linux. I like blueberry pie.
  • Test practice now: CPPUTest run with GCC
  • Target system: STM32
  • Dev tools: Keil, GCC, Eclipse
  • Build time: Under 10 seconds
  • Coding standard: Development, testing, review, pull request, more testing, sign off
  • Function too long: It no longer accomplishes a specific task or is no longer easily understandable
  • Code reviews: 3 or more people, 1 must be senior, 1 must be off platform
  • Code time: 50
  • Test time: 25
  • Debug time: 25
  • Favorite thing about dev: The challenges present with an embedded device and the ability to be creative with design and development
  • Least favorite thing about dev: Some of the politics required when making a design decision and the amount of testing required to prove the design out (with no unit testing)
  • Tdd knowledge: I have written a few very basic tests to get framework setup. Can improve confidence in development and result in less testing required afterward.
  • Why are you attending: Interested in best way to pull TDD into legacy code. We have a lot of code already written (but still under dev.) that have no reliable way to test (aside from bench testing) Looking to establish an automated way to verify software during development
  • Back