Course code: PRAQ-1
  • Years with company: 1
  • Years programming: 5
  • Primary programming language: C
  • Other programming languages: C++, Python
  • Unit test harnesses: CMocka
  • Something else: On my spare time I like to do outdoor activities, especially rock climbing.
  • Test practice now: Unit tests and target tests
  • Target system: nRF52. An SoC designed for low power wireless applications, mainly Bluetooth LE.
  • Dev tools: Keil, Visual Studio
  • Build time: 30-60 minutes
  • Coding standard: We have our own coding standard. Using some parts of Misra I think. We do have a lot of (old) code that don't follow the standard however.
  • Function too long: I don't know.. But a function should be comprehensible and the cyclomatic complexity must be limited.
  • Code reviews: We use CodeCollaborator. We have very productive reviews. Recently we started doing review kickoff meetings when the review is big or complex; this has been very useful.
  • Code time: 40
  • Test time: 30
  • Debug time: 30
  • Favorite thing about dev: Designing, discussing and implementing new features.
  • Least favorite thing about dev: That the requirements and priorities of the software changes quite often.
  • Tdd knowledge: That all the code is supposed to be unit testable and that you're supposed to write the unit tests before you actually code anything.
  • Why are you attending: I heard a lot about TDD and would like to find out if this is something I can use to become a more efficient and structured developer. How can I actually write unit tests before doing the coding?
  • Back