With regards to unit testing. I think it's a good idea and all but god it's such an awful task to undertake after you're thousands of lines deep in code.

nessquik is in need of a unit testing framework. It's not been demanded of me, but with the flakiness of the KCA code (which sucked to begin with) a hammer came down from above and mandated that testing frameworks be in place for all code that is written. Fine, I'm game, but god I didn't think it would be this much work.

Think of it as writing your whole application over again because that's basically what you're doing. There's a test for every function, and, logically, you should be able to test most if not all your code by running these tests. You call the function in question for the test.You read it's output and then compare it to pre-defined output. If you have a match, great. If you don't, then you have an error.

You create test classes for every method and function...lemme repeat, every method and function</strong>. For nessquik this is quite a big job because there are hundreds</strong> of methods and functions. Another tough part is generating the data that you know will be correct when you go to run your tests. nessquik generates some big</strong> data sets. According to the unit testing crowd though, this means that nessquik needs refactoring...great.

So that's what has been keeping me busy after I leave work each day. Or I mean, take my 15 minute break (drive home) from work...so that I can work at home. I tell ya, I'm going to burn myself out.