libtest-mockdbi-perl 0.70-1 source package in Ubuntu

Changelog

libtest-mockdbi-perl (0.70-1) unstable; urgency=low


  * Initial Release. Closes: #779445

 -- Christopher Hoskin <email address hidden>  Sat, 28 Feb 2015 17:45:57 +0000

Upload details

Uploaded by:
Debian Perl Group on 2015-03-03
Uploaded to:
Sid
Original maintainer:
Debian Perl Group
Architectures:
all
Section:
misc
Urgency:
Low Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Focal release on 2019-10-18 universe misc
Eoan release on 2019-04-18 universe misc
Disco release on 2018-10-30 universe misc
Cosmic release on 2018-05-01 universe misc
Bionic release on 2017-10-24 universe misc
Artful release on 2017-04-20 universe misc
Xenial release on 2015-10-22 universe misc

Builds

Wily: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
libtest-mockdbi-perl_0.70-1.dsc 2.3 KiB df7e733dfea754af1da68ae4e813bdd2a5e87460fe07430a2e4dc57eb24f32de
libtest-mockdbi-perl_0.70.orig.tar.gz 26.7 KiB 382ddd721c00b777ed6efadc26277f2bd75ab9a17c0e66481b9650902c6c48e4
libtest-mockdbi-perl_0.70-1.debian.tar.xz 2.1 KiB d25c6ea3a69b57a43392197508f6e664c40bc28ef9872dab9d03342c6f0922f2

No changes file available.

Binary packages built by this source

libtest-mockdbi-perl: mocked DBI interface for testing purposes

 Test::MockDBI has a major advantage over DBI::trace()
 or DBD::Mock -- Test::MockDBI lets you change how the
 mocked DBI functions behave, along with modifying
 what data is returned by the mocked DBI functions.
 These changes and modifications can be made specific
 to particular SQL statement patterns.
 .
 This ability to modify DBI function behavior and
 DBI-returned data makes it easier to test code that has
 different branches for different DBI behaviors -- you
 can test that a failure within DBI or returned DB data
 that is different than normal is processed correctly by
 your module or program. If you are taking over a large
 code base, Test::MockDBI will help in understanding the
 code by allowing you to safely check how the code behaves
 under different database conditions without modifying any
 databases (production or otherwise).