Course code: UBL-1
  • Years with company: 10
  • Years programming: 35
  • Primary programming language: C, C++
  • Other programming languages: Perl
  • Unit test harnesses: Created our own test framework for my team's tests. Some people have used cppunittest
  • Something else: .
  • Test practice now: In our test framework environment. The goal is to write a test first and then the code! It is designed to work both on target system as well as host builds.
  • Target system: Multi core ARM and proprietery processor embedded system
  • Dev tools: ARM DS5 tool chain Linux editors Visual Studio on Windows
  • Build time: 5-30 minutes
  • Coding standard: I wrote it! Like all standards, plenty to choose from. Coding standard varies across teams due to heritage of the teams but is conistent within teams.
  • Function too long: When it scrolls off the screen!
  • Code reviews: We use Swarm which is part of Perforce. Shelved changed lists can be reviewed by colleagues. We usually select a couple of colleages to peer-review out changes. Shelved changes are also tested in our pre-submit test system.
  • Code time: 33
  • Test time: 33
  • Debug time: 33
  • Favorite thing about dev: Solving problems
  • Least favorite thing about dev: Waiting hours for pre-submit test system to give results.
  • Tdd knowledge: Write the tests before writting the code. Write first test and code to pass test. Write second test, refactor code to pass first and second test. Interate to all tests and features completed! If a bug reported, write test to reproduce then fix.
  • Why are you attending: I member of my team saw the course and thought it would be a good thing to do.
  • Back