Course code: ETA-1
  • Years with company: 2
  • Years programming: 10
  • Primary programming language: C
  • Other programming languages: python
  • Unit test harnesses: NA
  • Something else: SW developer with background in customer support of ARM-Cortex-M devices. Now leading small team.
  • Test practice now: unit tests using ceedling + integration tests using proprietary HW platform.
  • Target system: watch :)
  • Dev tools: jlink + exlipse, KEIL, Jtrace
  • Build time: 1-5 minutes
  • Coding standard: internal company coding standard
  • Function too long: by feeling, by code reviews
  • Code reviews: using bitbucket for each pull request
  • Code time: 50%
  • Test time: 20%
  • Debug time: 30%
  • Favorite thing about dev: see it working
  • Least favorite thing about dev: see it not working by someone else
  • Tdd knowledge: forced by the management :) at the moment we do "reverse" TDD by just unit test the code.
  • Why are you attending: I'd like to understand if it makes sense to make real TDD for not only lesson examples but if it is really feasible to make it for any SW. I'd like to know best practices in TDD and to get answers to already prepared questions.
  • Back