Beefy Boxes and Bandwidth Generously Provided by pair Networks
Your skill will accomplish
what the force of many cannot

Comment on

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

I would have to agree with adrianh that the test suite is maybe not the place to do this. His suggestion about using the SCM comments is a good one, but I would take that a step further as well, and enter the information about the bug, how it was fixed, and where it is tested in some RT-like bug-tracking application.

... 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.
All this could then be accomplished by just viewing the comments about the bug. And since what you are asking to look at is really best viewed from the POV of the bug, the bug-tracking application seems to me the logical place for it.

As for how to accomplish this with your test-cases and test-plans, I would reccommend the same approach (assuming you have an application or document that keeps track of these things, and you can add information to said document).

Another thought might be to place specific bug-fix test code into seperate files, which are then included with do or some kind of pre-processing into the larger test suite. This would allow you to still retain the larger structure of the tests, while being able to keep the bug-fix tests in their own seperate files. This would allow you to reference that single file in your bug-tracking application, and put more in depth comments in the file. Of course you still need to worry about the tendency of comments and code to fall out of sync, but being that the whole file will be specific to this one bug-fix, it is possible this may not happen (at least not as easily).


In reply to Re: Organising Large Test Suites by stvn
in thread 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 all is quiet...

    How do I use this? | Other CB clients
    Other Users?
    Others rifling through the Monastery: (2)
    As of 2018-03-25 06:04 GMT
    Find Nodes?
      Voting Booth?
      When I think of a mole I think of:

      Results (300 votes). Check out past polls.