Course code: CONT-1
Years with company:
15 (professional); 23 (including hobby programming)
Primary programming language:
Other programming languages:
Java, C++, some web based and script languages
Unit test harnesses:
JUnit, Cantata++, Test Conductor
I'm convinced that with current known technologies, Model Driven Development with UML is the only good way to develop Software. This enables also TDD, since the use cases are designed/developed before the implementation is done.
What I'm trying to do is to convince also other people that they should go in that direction.
Test practice now:
Cantata++, mainly on black-box level, which also enables a white-box test, by having enough tests on interface level to execute all the internals (close to 100% branch coverage).
Different controllers, small targets, but I don't care a lot.
UML (Rhapsody), eclipse
Under 10 seconds
MisraC 2004 (planned is MisraC 2012)
Function too long:
If it doesn't fit a screen size.
No tool in place.
Favorite thing about dev:
It's more the design then the code. Clever object oriented patterns, as far as possible with C.
Least favorite thing about dev:
Runtime errors which can't be reproduced. And that they always come up when it is no time to analyse.
I like the idea. Generating first the test and then implementing the code that the test runs. But not always practical.
Why are you attending:
I hope to learn better concepts and better strategies, in order to detect what the important bits are (not quantity, but quality of the tests).