libtest-mockdbi-perl 0.70-2 source package in Ubuntu
Changelog
libtest-mockdbi-perl (0.70-2) unstable; urgency=medium [ Salvatore Bonaccorso ] * debian/control: Use HTTPS transport protocol for Vcs-Git URI [ gregor herrmann ] * debian/copyright: change Copyright-Format 1.0 URL to HTTPS. [ Salvatore Bonaccorso ] * Update Vcs-* headers for switch to salsa.debian.org [ gregor herrmann ] * debian/watch: use uscan version 4. -- Jelmer Vernooij <email address hidden> Fri, 17 Jun 2022 12:25:46 +0100
Upload details
- Uploaded by:
- Debian Perl Group
- Uploaded to:
- Sid
- Original maintainer:
- Debian Perl Group
- Architectures:
- all
- Section:
- misc
- Urgency:
- Medium Urgency
See full publishing history Publishing
Series | Published | Component | Section |
---|
Downloads
File | Size | SHA-256 Checksum |
---|---|---|
libtest-mockdbi-perl_0.70-2.dsc | 2.2 KiB | 15f39756077bc155f14db193e90dd274447bafa7b79b989b62071bba5931f77c |
libtest-mockdbi-perl_0.70.orig.tar.gz | 26.7 KiB | 382ddd721c00b777ed6efadc26277f2bd75ab9a17c0e66481b9650902c6c48e4 |
libtest-mockdbi-perl_0.70-2.debian.tar.xz | 2.4 KiB | a089bb1bfffc59b06e58d441924ab195e445aec138d48a754cc34564932dbf24 |
Available diffs
- diff from 0.70-1.1 to 0.70-2 (1.3 KiB)
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).