One way is to redirect stdout to a file. For this purpose it helps if the file is actually a Perl variable. Consider:

package Test_Package;

use strict;

sub testing {
   print "okay.";
};

1;

use strict;

use Test::More tests => 1;

my $log;

open my $logFile, '>', \$log;
my $oldStdOut = select $logFile;

Test_Package->testing();
select $oldStdOut;
close $logFile;

is($log, 'okay', 'Testing okay');

[download]

Prints:

1..1
not ok 1 - Testing okay
#   Failed test 'Testing okay'
#   at ...\noname.pl line 25.
#          got: 'okay.'
#     expected: 'okay'
# Looks like you failed 1 test of 1.

[download]

The error is deliberate btw.

True laziness is hard work

In reply to Re: How to Test Output from the Standard Output by GrandFather
in thread How to Test Output from the Standard Output by Anonymous Monk

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.