Course code: ROL-3
  • Years with company: 0
  • Years programming: 7
  • Primary programming language: C++
  • Other programming languages: C, python, java
  • Unit test harnesses: QtTest
  • Something else: I also use QML files for UI display and of course, Qt libraries.
  • Test practice now: Most of testing is done by manual testing. Few unit and integration tests (via QtTest) are written. But it doesn't cover full code.
  • Target system: Target system is under UNIX system. We have two main applications (frontend/backend) running and communicating between each other.
  • Dev tools: QtCreator CMake
  • Build time: 1-5 minutes
  • Coding standard: New part of code is written in english following camel case rule. Comments are put if reason to write part of code is not clear.
  • Function too long: I know when a function is too long when I need to scroll in IDE to read it.
  • Code reviews: We use merge request via Gitlab to validate or not modifications. At least two MMI members are put as reviewer.
  • Code time: 30
  • Test time: 40
  • Debug time: 35
  • Favorite thing about dev: I like to see the result.
  • Least favorite thing about dev: I don't like when classes are too much inter-depend, eg when you have to include many header files to develop your feature.
  • Tdd knowledge: Test should be written before implementation.
  • Why are you attending: Improve my skill to write tests. How to begin with new feature and how to proceed for correcting bugs?
  • Back