Course code: VIAVI-1
  • Years with company: 3.5
  • Years programming: 10
  • Primary programming language: C++
  • Other programming languages: Objective C
  • Unit test harnesses: Google test, XCTest
  • Something else: I have done some unit testing but I am still not comfortable with it. I would like to learn it so that I can improve my code quality.
  • Test practice now: Manual testing during development, Integration testing, occasional unit testing.
  • Target system: MTS network testing unit, iOS App
  • Dev tools: Eclipse, OpenGrok, Git
  • Build time: 1-5 minutes
  • Coding standard: Using best coding practices, smaller code changes in feature branches, mandatory code reviews
  • Function too long: When the function name doesn't accurately represent what it does.
  • Code reviews: I have code reviews for any code that I write.
  • Code time: 50
  • Test time: 20
  • Debug time: 30
  • Favorite thing about dev: Challenging, Working in teams
  • Least favorite thing about dev: Dealing with legacy code
  • Tdd knowledge: Write tests first, then write code to make them pass.
  • Why are you attending: I want to learn mainly how to test with so much legacy code around and exactly what behavior should I be testing of a class. Is it necessary to think of every single corner-case and write unit test for it? or only write them for the public interface.
  • Back