Beefy Boxes and Bandwidth Generously Provided by pair Networks
more useful options

Comment on

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

Further to What is the best way to add tests to existing code?, I need to organise a huge and growing test suite. In particular, I'm eager to learn good ways to map unit test programs to external sources -- such as bug-IDs, test-case IDs, test plans, and so forth.

For example, given a specific bug-ID, could you tell me: a) if it is being tested by the regression test suite; and b) which bit of unit test code actually tests that bug. Ditto for a specific test-case-ID/test plan.

Curiously, for the Perl core, given a particular RT ticket #, there is currently no easy way to tell which of Perl's 80,000-odd tests test for it. Or even if it's regression tested at all. (If you're lucky, you might find a reference to the RT ticket # in code comments and/or change logs).

There's been a lot of interest in code coverage, and Paul Johnson has done a wonderful job with Devel::Cover. What about bug coverage? That is, what percentage of your bug database is covered by your test suite? Which, btw, might make a nice kwalitee measure of CPAN modules.

You might partition your test suite into two pieces: one to test bugs raised in the field; the other to grow in-step with the code as you develop it (i.e. test-driven development). My current plan is simply to insert bug-IDs/test-case IDs in test program comments and Configuration Management change logs. How do you do it?

In reply to Organising Large Test Suites by eyepopslikeamosquito

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, 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
  • 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.
  • Log In?

    What's my password?
    Create A New User
    and one hand claps...

    How do I use this? | Other CB clients
    Other Users?
    Others scrutinizing the Monastery: (9)
    As of 2018-06-18 19:32 GMT
    Find Nodes?
      Voting Booth?
      Should cpanminus be part of the standard Perl release?

      Results (110 votes). Check out past polls.