I have been putzing with unit testing frameworks all week. I could not find one I really liked. First a lot were too complicated for my purposes. Most of my unit testing exercises computation. Making sure 1 + 1 is 2, is what I really , really need. The other gripe I had is the text file output. I want somewhat is databaseable. I want to look back and see when something stopped working, with out digging thru a lot of files or doing the svn thing. You know, pulling out old copies, running the unit tests to see where things broke. Granted, I only had to do that a few times, mainly when I had a busted import into svn. Oh, and I wanted the same output accross implementations since the interfaces will be developed in parallel.

So I decided to write my own. Not as featured as JUnit, CUnit, G-Unit , but functional. It has databaseable output and fits in a header file in C++. So that is getting dumped into svn, but it won’t be in the release for a while.

And I know databasable and putzing are not real words.