Course code: WEB-34
  • Years with company: 3
  • Years programming: 20
  • Primary programming language: C
  • Other programming languages: C++ Python C#
  • Unit test harnesses: Proprietary, H/W electrical
  • Something else: Career focused on development. Company culture and career has not been so much focused on test in 'commerical' non-safety critical settings.
  • Test practice now: Ad-Hoc test using debugger. Write simple test code or scripts along with developed code, but not systematically done.
  • Target system: Embedded IOT device with cellular, WIFI, Bluetooth connectivity
  • Dev tools: Eclipse-based compiler, debugger. Infrequent use of Google-Test.
  • Build time: 5-30 minutes
  • Coding standard: Has variable/function naming and style conventions for consistent look. Some rules regarding modularity. Process mandates code review.
  • Function too long: More than two screen pages or function does multiple things which start to become unrelated.
  • Code reviews: Use JIRA to review most if not all changes and features.
  • Code time: 90
  • Test time: 10
  • Debug time: 10
  • Favorite thing about dev: Like to make things work and see things run
  • Least favorite thing about dev: Unsure
  • Tdd knowledge: Development is performed around the question, how can this be tested and/or verified?
  • Why are you attending: A lot of my career has been focused on development not test, need to develop skills from unit-test to functional, script driven test. Wish to lean good practice methods and accepted 'standards' for doing this.
  • Back