I spent the whole day writing JUnit tests for the infrastructure of a CMSish Cocoon-based application that I’m working on.
This is my first serious app using OJB for persistence, and the learning benefits of writing automated tests are huge.
Stressing the system with just a few lines of nasty code makes bugs (mine in this case, OJB behaves very well) surface very quickly – I’ve learned at least ten important things about OJB today, and without this it would have taken much longer.
I’m really getting test infected, and I like it!
Red, green, refactor…time to hit the swimming pool ;-)
Note that there’s only one thing that I hate in OJB, it’s the acronym: I find myself typing OBJ instead of OJB about a million times a day. Too much ojbect-oriented programming I guess…