OK, after some digging :) 
use strict;
use warnings;
use Test::More;

Test::More->builder->output(\ my $scalar);

is($_,$_,"equality $_") for 1..10;

is(1,0,"FAIL"); 

done_testing;

[download]

C:/Strawberry/perl/bin\perl.exe -w d:/tmp/pm/redirect_Tests.pl 
#   Failed test 'FAIL'
#   at d:/tmp/pm/redirect_Tests.pl line 11.
#          got: '1'
#     expected: '0'
# Looks like you failed 1 test of 11.

[download]

... but it will still fill up $scalar with the passed tests.

Does Perl have a generic /dev/null filehandle to ignore output like on linux?

edit

this works on Win, but it's not generic

open my $null,">","nul";

Test::More->builder->output($null);

[download]

update

Ah yes IO::Null is on cpan. :)

Cheers Rolf
(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery

In reply to Re: Test::More to only report fails? by LanX
in thread Test::More to only report fails? by LanX

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.