There are a few mocking distributions on the CPAN, but I'll show an example using my Mock::Sub. You can mock out subs, then tell it to do something (side_effect()), or return something (return_value()). Instead of using a method to set them, you can also specify them in the constructor if you choose (then remove/modify them with the methods later):
use warnings;
use strict;
use lib '.';
use Mock::Sub;
use Test::More;
use Utils::Ldap::CompanyLdap;
my $m = Mock::Sub->new;
my $ldap = Utils::Ldap::CompanyLdap->new;
my $mocked_sub = $m->mock(
'Utils::Ldap::CompanyLdap::searchGetEntries'
);
$mocked_sub->return_value(qw(steve mike dave));
read_users();
is $mocked_sub->called, 1, "searchGetEntries() called ok";
sub read_users {
for my $entry ($ldap->searchGetEntries()){
print "$entry\n";
}
}
done_testing();
Output:
steve
mike
dave
ok 1 - searchGetEntries() called ok
1..1
-
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.
|