Ubuntu
libdbd-mock-perl package

libdbd-mock-perl 1.43-1 source package in Ubuntu

Changelog

libdbd-mock-perl (1.43-1) unstable; urgency=low

  * New upstream release.
  * Add a patch to fix a spelling mistake in the POD.

libdbd-mock-perl (1.42-1) unstable; urgency=low

  * New upstream release.
  * Remove patch fix-pod-spelling: applied upstream.
  * Add build-dep on libtest-exception-perl (>= 0.31).
  * debian/control: Convert Vcs-* fields to Git.
 -- Ubuntu Archive Auto-Sync <email address hidden>   Mon,  17 Oct 2011 11:04:18 +0000

Upload details

Uploaded by:
Ubuntu Archive Auto-Sync
Uploaded to:
Precise
Original maintainer:
Debian Perl Group
Architectures:
all
Section:
perl
Urgency:
Low Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Precise release universe perl

Builds

Precise: [FULLYBUILT] i386

Downloads

File Size SHA-256 Checksum
libdbd-mock-perl_1.43.orig.tar.gz 47.2 KiB 528dd5cdf2d813fcb1d74956b10925cfc5bc0ac6df43bf3061c8ef4d112df2ac
libdbd-mock-perl_1.43-1.debian.tar.gz 3.1 KiB 3caba8f167d52295a8565cca0a38da3e47750e9356e6ccf8c517c854ad2a3fde
libdbd-mock-perl_1.43-1.dsc 2.1 KiB 1c9b6d2d8c8438256595145f3d4b33a738f5f7eb1cfb671635bbe29da9a080b1

Available diffs

View changes file

Binary packages built by this source

libdbd-mock-perl: Mock database driver for testing

 Testing with databases can be tricky. If you are developing a system married
 to a single database then you can make some assumptions about your
 environment and ask the user to provide relevant connection information. But
 if you need to test a framework that uses DBI, particularly a framework that
 uses different types of persistence schemes, then it may be more useful to
 simply verify what the framework is trying to do -- ensure the right SQL is
 generated and that the correct parameters are bound. DBD::Mock makes it easy
 to just modify your configuration (presumably held outside your code) and
 just use it instead of DBD::Foo (like DBD::Pg or DBD::mysql) in your
 framework.