Monks,

When running a 'make test' (obtained from module-starter) all module output is suppressed. The test in t/ are called using test_harness() which uses TEST_VERBOSE. Setting TEST_VERBOSE to other values than 0 enables print DEBUG statements from the .t files, but not from the modules themselves. Commenting NOECHO does not do it either. What is the regular approach when trying to debug a module in this context ? Or, is it that modules are usually not debugged when running 'make test' ? I could make a test program to debug the modules out of 'make test' so module console output is allowed, although I kind of expected that this could be done while running 'make test'.

Thanks for any suggestions/ideas/comments.

Best wishes to all for 2010!

In reply to Module testing inside test_harness: verbose output ? by carcassonne

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.