Course code: AS-1
  • Years with company: 2
  • Years programming: 5
  • Primary programming language: C
  • Other programming languages: Python C++
  • Unit test harnesses: None
  • Something else: I've never written tests for my code beofre
  • Test practice now: By running it on the target. With debugger, print statements or normal operation depending on how much has changed.
  • Target system: Embedded systems, STM32
  • Dev tools: Git, Gitlab, Jira, Eclipse, Visual Studio Code
  • Build time: 11-30 seconds
  • Coding standard: Mostly focused on whitespace, naming, styles.
  • Function too long: When it becomes too complex to keep track of what it does.
  • Code reviews: One or more relevant persons will look through the changes and confirm it does what it is supposed to and adheres to the defined coding guidelines. The author is responsible for testing the code and making any requested changes.
  • Code time: unknown
  • Test time: unknown
  • Debug time: unknown
  • Favorite thing about dev: Lots of interesting, unique challenges.
  • Least favorite thing about dev: Debugging situations where unknown physical phenomena is affecting the result.
  • Tdd knowledge: You start by defining the interface, write test that test that the output is correct, then write the actual code.
  • Why are you attending: Because I was assigned to attend it. That sounds unenthusiastic, but it's the simplest truth. I hope to learn enough to begin with test driven development and reduce time spent debugging and confirming a change didn't break something unknown.
  • Back