Course code: CIR-1
  • Years with company: 1
  • Years programming: 20
  • Primary programming language: C
  • Other programming languages: C++ Python Perl Ruby
  • Unit test harnesses: Embunit
  • Something else: I am an experienced embedded software engineer
  • Test practice now: Unit tests System-level test Touch test (manual exercise of some subset of use cases)
  • Target system: Cirrus DSP
  • Dev tools: Toolchain provided by Synopsys including their IDE Notepad++ SonarQube cppcheck
  • Build time: 5-30 minutes
  • Coding standard: Documented coding standard which is validated in review and via cppcheck / SonarQube / CheckStyle / vera++
  • Function too long: Reviewers moan. It clearly doesn't fit in one or two screens worth of view. Failure of SonarQube complexity metric.
  • Code reviews: We use CodeCollaborator for online code review - at least 2 reviewers per review
  • Code time: 20
  • Test time: 20
  • Debug time: 20
  • Favorite thing about dev: Logical problems
  • Least favorite thing about dev: Unexplained failures
  • Tdd knowledge: Not much beyond inference from the title
  • Why are you attending: It might give some useful insights for how I can improve the design/implementation/time-line of test suites for new projects - perhaps they shouldn't be knocked out after the main project development
  • Back