Jean-Hugues ROBERT wrote:
> This is definitely nice to me. Additionaly I don't like so much the idea of large distance between the code and the test code. But in your scheme a least part of the test code is close, right before the tested code, that's good I think.

My current gripe with unit test code is that they're the ugliest code I 
write :-). There are lots of duplication (from copy-and-paste), 
no/little modularization, full of quick 'n' dirty hacks, and I write 
them often without thinking about maintenance at all.

I think this is also true for most unit tests out there. If you want to 
look at the worst spaghetti code, look at the unit test :-)

-- 
dave