Beefy Boxes and Bandwidth Generously Provided by pair Networks
Keep It Simple, Stupid
 
PerlMonks  

Comment on

( #3333=superdoc: print w/ replies, xml ) Need Help??

This is a specific example of code coverage analysis, or “test coverage analysis,” and it is, as you will see, a relatively big topic.

Most commonly, the approach that is taken is to start with test-cases and to seek to analyze in an automatic or computer-assisted fashion which portions of the code are, and are not, covered by those cases.   While this is more or less the reverse of the approach that you are looking for, it is also a much more solveable problem in the general case.   Also, it tends to be more useful.   A system of conditional-tests is in effect a (not-necessarily binary) tree, which of course can produce a frighteningly-large number of unique possibilities, not all of which will be meaningful.   (It also cannot mechanically consider the overall context in which the piece of source-code under test might be encountered ... a critical factor which might be an NP-complete [unsolvable ...] problem or nearly so.)   Understanding of a real-world program ordinarily involves a level of semantic (i.e. “human”) understanding and guidance that cannot be truly eliminated, hence the approach that starts with tests and then evaluates those tests.   But testing-gap analysis can be done, and in a critical software system must be done.


In reply to Re: reverse engineering the input needed for full coverage of the program by sundialsvc4
in thread reverse engineering the input needed for full coverage of the program by david2008

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!
  • 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, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • Outside of code tags, you may need to use entities for some characters:
            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.
  • Log In?
    Username:
    Password:

    What's my password?
    Create A New User
    Chatterbox?
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others rifling through the Monastery: (6)
    As of 2014-09-02 01:07 GMT
    Sections?
    Information?
    Find Nodes?
    Leftovers?
      Voting Booth?

      My favorite cookbook is:










      Results (18 votes), past polls