A new testing methodology?
I try and always program using test driven development , and just like I feel a little scared when I drive, even a short distance, without a seatbelt on - I now feel a little scared when I program without a full suite of automated unit tests to back me up. It's really a great way to program. Sometimes, when I get tired or uninspired with regards to programming, I'll look at my tests cases and make sure that I'm testing everything. And whenever I find a bug, the first thing I do is create a test case that show's the bug, and eventually, proves that the bug has been fixed.
I started noticing that I often did the same thing - I would create these little files for input and another for the expected output. Then the test program would take the input, create output in a temporary file and then compare that output with the expected output. I'd leave the temp output around in case it doesn't match.
Then one day I had to do some tests for xml2ddl . The tests I wanted...