I'd say don't use do. If you've got the test notebook you can find the sample for a smoke test on p57, something like this (incomplete code)-

my $strap = Test::Harness::Straps->new(); for my $test ( <path/to/tests/*.t> ) { # warn/debug "Running test: $test\n"; my %result = $strap->analyze_file( $test ); next if $result{passing}; # Build report on failing results here # to present in an Ajax'd div or something. }

You might accidentally fix it by not using do and you should at least track the problem down to a single test otherwise.

Update: s/frame/div/; I did not mean a literal HTML frame.


In reply to Re: Running test filese from a cgi by Your Mother
in thread Running test files from a cgi by cosmicperl

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.