Course code: BARR-6
Years with company:
Primary programming language:
Other programming languages:
Unit test harnesses:
Qt test framework, google test
I am curious to see how TDD can be used without having to spend too much time writing tests.
Test practice now:
Mainly functional testing, by running the code on the target hardware and manually check the behavior.
Linux kernel coding style.
Function too long:
Too many lines of code. When it has more than one role.
Reviews are "created" manually after submitting code. The developer is responsible for creating or not a review and for selecting the reviewers and observers.
Favorite thing about dev:
I like the ability of "seeing the results" of my code, when it impacts the user experience and adds new features.
Least favorite thing about dev:
Code tends to become untidy or obsolete too fast.
I started doing TDD for less than a year in my previous company. We spent a lot of time learning how to write tests, but we progressively stopped writing tests because of time constraints.
Why are you attending:
This is part of an effort of introducing TDD in our work environment. I hope to learn new ideas and techniques that I can introduce easily to my team.