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

In reply to Re: Code Analysis Tools? by mr.dunstan
in thread Code Analysis Tools? by mr.dunstan

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.