Whoo, I think I asked a 2-prong question, which was not necessarily exactly the question I was trying to ask, but in hindsight, is still, I think, a pretty good one ...

We -are- actually using Silk to do our automated testing! I didn't hear the rumor though, thanks for the info! I guess it works fairly well as long as our test engineers can keep up with UI changes.

The thing I'm really thinking about should actually be called a "code validator", I think.

It would make sure all SQL queries in the code were at least somewhat sane, hopefully figure out an automatic way to test individual subs/methods, figure out if/when/where we've got really nasty duplication, and mainly to figure out what breaks if I change this little piece of obscure code over here .... hmm ... *sound of code breaking noisily*

Maybe I should just pray to the Perl Buddha instead!

PS: ovid - that's a nice piece of code there. Code that makes other code is always super super cool in my book! The next time I get to do a ground-up project I am most certainly going to do some kind of component generation if I can! It makes sense and it's so sheik!!


regards,
-mr.dunstan