Course code: WEB-11
Years with company:
Primary programming language:
Other programming languages:
C#, Python, Java, C
Unit test harnesses:
TUT, nUnit, hippomocks, CUTE
I like to lift heavy stuff and drink wine!
Test practice now:
Unit testing using TUT and mocking with hippomocks. I also write higher level functional testing using nUnit. nUnit interfaces with our product as the users tablet would.
Embedded system, iMX51 platform.
SVN, Visual studio 2008
We have a coding standard defined in a document which I try to adhere to. Beyond that I try to reduce dependencies and utilize dependency injection to make for easier testing.
Function too long:
Generally I think the most important thing is that a function should have only one function. But if a function does not fit on the screen all at once its def. too long.
We don't do code reviews often. When we do them they are quite informal, mostly someone just has a look at the SVN changes or you go through them together.
Favorite thing about dev:
When you feel like you have written some quality code that is reusable and well tested.
Least favorite thing about dev:
Writing ugly fixes due to time constraints. Working in code that should have been refactored long ago.
I't was part of some courses at the university so I think I have a general grasp of the concept.
Write tests first.
Build and run tests fast.
Done when tests pass.
Why are you attending:
I think TDD is a good concept but haven't used it a lot in practice as an embedded developer. So I'm hoping to learn some good ways to make it work in an embedded environment.