Assuming your module takes over STDERR, and then relies on the behavior of croak (or, really, die) to write to STDERR, I don't think you'll get your tests to work with eval, which supresses the write to STDERR. You may be better off using a signal handler:
local $SIG{__DIE__} = sub {
local $|++; # autoflush
print STDERR @_;
};
unlink 'test.errors';
redirect_error( output_file => 'test.errors' );
# call this directly, not in an eval, as you're trapping the croak
lcroak "this is a sample error file";
ok( -T 'test.errors',
"lcroak opens the error file specified by redirect_error()." );
my $text = `cat test.errors`;
like( $text , qr/this is a sample error file/,
"lcroak writes to the error file specified by redirect_error()." )
+;
unlink 'test.errors';
Picking a nit -- cat test.errors isn't portable. You may want to use File::Slurp or the equivalent and keep it in Perl.
Also, if you want to do this test by running a separate process, I'd suggest trying IPC::Run3 instead of using a system call. It will nicely redirect STDOUT and STDERR into scalar variables for you:
run3 \@cmd, undef, \$out, \$err;
-xdg
Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.