Course code: PASA-1
  • Years with company: 5
  • Years programming: 15
  • Primary programming language: C, C++
  • Other programming languages: Python, Java
  • Unit test harnesses: GTest, GMock, Cppunit
  • Something else: Have experience developing in all layers of software stack.
  • Test practice now: Mainly integration testing or sanity testing. Limited / No unit testing.
  • Target system: Arm based running QNX OS.
  • Dev tools: compilers/linkers, Debuggers, post mortem analysis (gdb), profilers, Eclipse based IDE (QNX Momentics),
  • Build time: 5-30 minutes
  • Coding standard: We have one somewhere .. but each developer ends up using his or her own standard!
  • Function too long: when I cant see it all in one screen (~30 lines).
  • Code reviews: use code collaborator to review code.
  • Code time: 50%
  • Test time: 20%
  • Debug time: 30%
  • Favorite thing about dev: Getting features working. Making code scalable Code should be maintainable and easy to understand.
  • Least favorite thing about dev: Code that is hard to understand (eg legacy code that is monolithic) Debugging issues that should have been identified early in the development lifecycle.
  • Tdd knowledge: It is a paradigm of developing test cases from requirements and code to pass these test cases.
  • Why are you attending: 1. To better understand TDD. It is not clear how TDD flow would ensure the customer requirements are met. 2. Best practices to make TDD successful 3. The challenges faced & addressed due to the churn due to refactoring
  • Back