In terms of good design, the previous replies are right on the money. But if you are unable to restructure your code as they suggest, it is still possible to test what you are asking.

You can localize STDERR and STDOUT to filehandles which write to scalars. Then call the method and check that the scalars contain what they should:

use Test::More 'no_plan';

my $status = Status->new;
my ($stderr, $stdout);

{
  local(*STDERR, *STDOUT);
  open STDERR, ">", \($stderr = "");
  open STDOUT, ">", \($stdout = "");

  $status->status("good");
}
ok( ($stderr eq "") and ($stdout =~ /good status/) );

###

{
  local(*STDERR, *STDOUT);
  open STDERR, ">", \($stderr = "");
  open STDOUT, ">", \($stdout = "");

  $status->status("bad");
}
ok( ($stderr =~ /bad status/) and ($stdout eq "") );
[download]

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.