Course code: WEB-16
  • Years with company: 14
  • Years programming: 14
  • Primary programming language: C
  • Other programming languages: Python
  • Unit test harnesses: unity
  • Something else: I am a person with big curiousity. This curiosity is directed to many different topics like the nature, hiking, reading books or having a good conversation (yes, that is very Spanish :)). I have a in Master in Physics and also in Electronics.
  • Test practice now: In-system debugging Blackbox tests
  • Target system: Our applications are energy harvesting or low powered radio transceiver/transmitters. Current micontroller platform is STM32L0 (ARM-M0 core). We also worked with MSP430, 8051 platform and Microchip 18F, 16F and 12F families.
  • Dev tools: Keil ┬ÁVision with ARM compiler. In the past also IAR-ARM/MSP430 and MPlab
  • Build time: 11-30 seconds
  • Coding standard: Internal coding guidelines
  • Function too long: When it implements different functionalities instead of being focused on one single task. Length also plays a role. And I assume testability plays another role.
  • Code reviews: Done/documented by another partner before product is going to be released.
  • Code time: 45
  • Test time: 55
  • Debug time: 5
  • Favorite thing about dev: I enjoy putting ideas into a system with a well structured logical behaviour.
  • Least favorite thing about dev: Having bugs on the field.
  • Tdd knowledge: It is a methodology to test while developing the sw (instead of after having developed the software) to improve sw quality and speed up development.
  • Why are you attending: Because I want to learn how to test while developing in a more systematic way. Also because other collegues found the ideas/methods in the course very useful.
  • Back