Here is a little snippet I use in tests. It's useful for checking for specific log messages.
use Test::More 'no_plan';
use Test::MockObject;

my $mock_logger = Test::MockObject->new;
$mock_logger->fake_module('Log::Log4perl',
  get_logger => sub { $mock_logger } );
@Log::Log4perl::EXPORT_OK = qw( get_logger );
$mock_logger->set_true( qw( debug info warn error fatal ));

# execute some code that uses Log::Log4perl...

my ( $method, $args ) = $mock_logger->next_call;
is( $method, 'debug', 'log is a debug message');
is( $args->[1], 'bomb is ticking',
  '... with the expected text');

[download]

In reply to testing log messages by jczeus

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.