File: control

package info (click to toggle)
libtest-mockdbi-perl 0.70-1
  • links: PTS, VCS
  • area: main
  • in suites: buster, stretch
  • size: 376 kB
  • ctags: 112
  • sloc: perl: 954; makefile: 2
file content (45 lines) | stat: -rw-r--r-- 1,778 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
Source: libtest-mockdbi-perl
Section: perl
Priority: optional
Maintainer: Debian Perl Group <pkg-perl-maintainers@lists.alioth.debian.org>
Uploaders: Christopher Hoskin <christopher.hoskin@gmail.com>
Build-Depends: debhelper (>= 9)
Build-Depends-Indep: libclone-perl,
 libdbi-perl,
 libtest-differences-perl,
 libtest-mockobject-perl,
 libtest-warn-perl,
 perl (>= 5.13.10) | libcpan-meta-perl,
 perl
Standards-Version: 3.9.6
Vcs-Browser: https://anonscm.debian.org/cgit/pkg-perl/packages/libtest-mockdbi-perl.git
Vcs-Git: git://anonscm.debian.org/pkg-perl/packages/libtest-mockdbi-perl.git
Homepage: https://metacpan.org/release/Test-MockDBI
Testsuite: autopkgtest-pkg-perl

Package: libtest-mockdbi-perl
Architecture: all
Depends: ${misc:Depends}, ${perl:Depends},
 libclone-perl,
 libdbi-perl,
 libtest-differences-perl,
 libtest-mockobject-perl,
 libtest-warn-perl
Description: 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).