Quick Navigator

Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Contact Us
Online Help
Domain Status
Man Pages

Virtual Servers

Topology Map

Server Agreement
Year 2038

USA Flag



Man Pages
mocked(3) User Contributed Perl Documentation mocked(3)

mocked - use mocked libraries in unit tests

  # use a fake LWP::Simple for testing from t/lib/LWP/
  use mocked 'LWP::Simple';
  my $text = get($url);
  # use a fake WWW::Mechanize for testing from t/mock-libs/WWW/
  use mocked [qw(WWW::Mechanize t/mock-libs)];

Often during unit testing, you may find the need to use mocked libraries to test edge cases, or prevent unit tests from using slow or external code.
This is where mocking libraries can help.
When you mock a library, you are creating a fake one that will be used in place of the real one. The code can do as much or as little as is needed.
Use as a safety measure (be sure you're actually using the mocked module), and as a way to document the tests for future maintainers.

The real @INC that we are over-ridding is stored here while we are loading the mocked library.

With a package name, this function will ensure that the module you specify is loaded from t/lib.
You can also pass an array reference containing the package name and a directory from which to load it from.

Luke Closs, "<cpan at>" Scott McWhirter, "<kungfuftr at>"

Ingy döt net, for

This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

Hey! The above document had some coding errors, which are explained below:
Around line 112:
Non-ASCII character seen before =encoding in 'döt'. Assuming UTF-8
2007-12-11 perl v5.28.1

Search for    or go to Top of page |  Section 3 |  Main Index

Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with ManDoc.