Course code: ELSTER-1
  • Years with company: 2
  • Years programming: 10
  • Primary programming language: C
  • Other programming languages: C++, Python
  • Unit test harnesses: unittest/nose
  • Something else: Graduated from University of Illinois at Urbana-Champaign
  • Test practice now: python sanity tests using unittest/nose, manual testing
  • Target system: ARM Cortex M4
  • Dev tools: IAR/Visual Studio
  • Build time: 31-60 seconds
  • Coding standard: Our coding standard describes how the code should look, how to avoid confusion, and how to avoid prevent bugs. The standard is not always strictly followed, i.e. whether or not to put a space in an 'if ()'
  • Function too long: If the function is doing too many things or I can't immediately tell where it ends.
  • Code reviews: We use a combination of ReviewBoard and in person reviews. People typically review the code ahead of time and come to the reviews with questions or concerns. When changes are made, developers will send out another review of the corrections.
  • Code time: 20
  • Test time: 40
  • Debug time: 40
  • Favorite thing about dev: The challenges of working with an embedded system where hardware and platform constraints must be considered.
  • Least favorite thing about dev: Documentation can be tedious.
  • Tdd knowledge: Test cases are written first. Functionality is developed for the test cases and then that functionality is tested. In C, I believe the tests are supposed to be in the C code.
  • Why are you attending: Recommended by management. I am interested in seeing how TDD can fit into what we do and how it makes developing and testing more efficient.
  • Back