Course code: VOL-1
  • Years with company: 5
  • Years programming: 1
  • Primary programming language: C++
  • Other programming languages: Python
  • Unit test harnesses: Google test/Gmock
  • Something else: Requriement and systems engineer for many years, decided to convert to software development and now think I should have done that a long time ago ;-)
  • Test practice now: Unit testing and SW component testing with google test Black box testing HIL with pytest.
  • Target system: Telematics system, two CPUs + power CPU (ARM), one handling vehicle interfaces
  • Dev tools: VSCode, Eclipse, Git, PC lint, Jenkins, Bullseye code coverage
  • Build time: 11-30 seconds
  • Coding standard: We have our own homebrewed coding standard in our project (it is a huge project) but it is not very strict at all. Using PC lint (and of course the compiler) to enforce standards.
  • Function too long: Oh, good question. I tend to break a function up in "helpers" when the code readablity subjectively is low. Don't have any strict (or any) rules about this in project.
  • Code reviews: We use Atlassian tool chains at Volvo -> Bitbucket for reviews
  • Code time: 30
  • Test time: 60
  • Debug time: 10
  • Favorite thing about dev: I love solving problems and seeing the product of my work quickly (not so much like that when working in systems engineering)
  • Least favorite thing about dev: Dependency frustration and being blocked by other teams.
  • Tdd knowledge: A little, working on practicing it in daily work (although have to admit it is easy to fall into old patterns of coding first and testing later, especially when doing changes in existing code)
  • Why are you attending: Because I am actually really interested in understanding how I can work TDD for real.
  • Back