Course code: WEB-29
  • Years with company: 0
  • Years programming: 10
  • Primary programming language: C++
  • Other programming languages: C, C#, some Java (but rare). I've messed with Bash scripting, Batch scripting, and Perl but I normally have to google what I want to do.
  • Unit test harnesses: Microsoft Test Manager in Microsoft TFS - very long time ago.
  • Something else: I enjoy embedded development very much and am eager to take this course. Also spend my free time learning an instrument (guitar).
  • Test practice now: New to company, they use CPPUnit. Past company we tested per requirements on a hardware rig, then we had a validation/test group that did formal testing, using custom scripting / hardware to exercise the software. It was for aviation related equipment; so we had to have a validation group certify the code and package it up to get sent to the FAA for approval. Lots of custom tools used to test that stuff.
  • Target system: ARM Cortex M3 chip.
  • Dev tools: IAR compiler, Cygwin, CppUnit
  • Build time: 11-30 seconds
  • Coding standard: Mainly follows MISRA 2012 standard.
  • Function too long: Based on what ever the coding standard states. If I remember correctly they rather you limit functions to 50 lines.
  • Code reviews: Done using Jira and Bitbucket.
  • Code time: 60
  • Test time: 20
  • Debug time: 20
  • Favorite thing about dev: I enjoy thinking logically, and writing software. I believe makes you better at analyzing problems.
  • Least favorite thing about dev: If you're not proficient with pointers, you're in for some headaches. My last job, the software was large, it took up to 30 minutes to build from scratch. Once built, changes normally took 30 seconds to a minute.
  • Tdd knowledge: The book has a bee on it. You write the testing code before the application code.
  • Why are you attending: Firmware group wants everyone to write unit tests. I was hired on, and they said they do this. So now I'm going to learn how to do it.
  • Back