Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

Ovid (2709)

Ovid
  (email not shown publicly)
http://publius-ovidius.livejournal.com/
AOL IM: ovidperl (Add Buddy, Send Message)

Stuff with the Perl Foundation. A couple of patches in the Perl core. A few CPAN modules. That about sums it up.

Journal of Ovid (2709)

Thursday August 21, 2008
04:34 AM

Test::Harness ouput change

[ #37242 ]

It's just a minor change that both Andy and I have wanted for a long time, but I do wonder if it will impact others. Instead of seeing this (use.perl inserts extra spaces, so this might not line up right):

t/proverun......................ok
t/regression....................ok
t/result s.......................ok
t/scheduler.....................ok
t/source........ ................ok
t/spool.........................ok
t/state................. ........ok
t/streams.......................ok

You'll see this:

t/proverun .................... ok
t/regression .................. ok
t/results ..................... ok
t/scheduler ................... ok
t/source ...................... ok
t/spool ....................... ok
t/state ....................... ok
t/streams ..................... ok 

Both of us found this much cleaner. However, this might have unexpected consequences. It also highlights the issue of Test::Harness's long-standing practice of stripping the .t extension from filenames. Why? If we want other extensions, stripping them is probably bad.


List all Journal entries
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Test::Harness ouput change 11 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • CPAN::Reporter ignores that and just looks for the grade at the end, so green light from me.

    What do you do if the test file name is longer than your fixed column width?

    t/something/something-else/with-a-long-long-long-long-test-name.t

    -- dagolden

  • While we are on the topic of Test::Harness output, a change that I'd like to see is padding of the test number so that test comments are aligned.

    For example consider the following trimmed down test program and output:

    use Test::More tests => 11;

    for (1 .. 11) {
        is(1, 1, 'This is a comment');
    }

    __END__

    perl output1.t
    1..11
    ok 1 - This is a comment
    ok 2 - This is a comment
    ok 3 - This is a comment
    ok 4 - This is a comment
    ok 5 - This is a comment
    ok 6 - This is a comment
    ok 7 - This is a comment
    ok

    • I like this thought because things which improves comprehension are good, but there are a couple of issues here. First, many test descriptions (what you're referring to as a comment), are often close to the width of whatever terminal I'm working with, so pushing them out even further may be problematic. Second, since we don't always know up front how many tests will be run, we won't know what padding would be needed.

      However, rather than a specific solution like this, how about a more general one?

      prove -r

      • There’s not much we could do to stop that

        You could generate a test message with this format and try to parse it and see that the parts all where you expected them. (Should the parts be randomly generated so the user can’t fool you?) If that fails you tell the user that their format is no good and bail.

        • Should the parts be randomly generated so the user can’t fool you?

          Ah, no, there is a simpler way, which is to try twice, with messages that differ in all parts.

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.