It's great to see that I'm not completely crazy. I mentioned building a test harness to my area a few years ago and I was laughed at! Every person on my team asked me "why would we want to do that?" "That's a waste of time!" Now, we struggle to get anything tested properly, test scripts are too high-level and as a developer, I've had to resort to validate test results from testers to ensure that quirks weren't dismissed as "features." Yes, to a test harness! Also, it doesn't take expensive software to test code. Experience, knowledge and creativity should be able to get most to the point of coming up with a solid way to test code/apps. And yes, nothing new about all this. I definitely feel that having a test plan in mind/on paper when stuff is being coded is a great idea. This can actually help to keep stuff getting too far off of spec since you will know up front how to test your destination and with that in mind, you most likely will know as you are coding if what you are doing anything that will cause you to miss your mark ( go off spec).