Course code: BLUE-1
  • Years with company: 5
  • Years programming: 20
  • Primary programming language: C++
  • Other programming languages: Python, Java
  • Unit test harnesses: CppuTest, Junit
  • Something else: Working in the IGS Team, for just over a year now. Was in Enterprise Systems for 4 years before that, founding member of the Blue Data Management System team. That was Java. IGS is older code in C++, not written for easy unit testing, ie classes and methods that are huge and have cross domain responsibilities.
  • Test practice now: The most useful tests today are all manual and take a lot of time. We have some unit tests using cpputest, and it's growing, but at current levels benefits have not outweighed efforts....yet.
  • Target system: Linux, Windows
  • Dev tools: Qt Creator, NetBeans, Spyder
  • Build time: 1-5 minutes
  • Coding standard: CMFM-PR0003_Safety_Critical_C++_Coding_Standards
  • Function too long: rule of thumb, when you have to scroll to read it, but really depends on what it does, some cases, 5 lines could be too long
  • Code reviews: Usually too big, so suggestions rarely cause a noticeable impact
  • Code time: 40
  • Test time: 40
  • Debug time: 20
  • Favorite thing about dev: Ability to plan/architect, implement and fine tune implementation, all within a relatively short time.
  • Least favorite thing about dev: Manual Testing and writing unit tests for classes/methods that are not written with unit testing in mind.
  • Tdd knowledge: I have managed a team where 2 people paired to leverage TDD successfully, over 10 years ago. I did not do TDD myself, but created the environment so they had the freedom to execute, was supportive, and was able to observe.
  • Why are you attending: I would like to try this for myself, really.
  • Back