File: control

package info (click to toggle)
libtest-tabledriven-perl 0.02-1
  • links: PTS, VCS
  • area: main
  • in suites: bullseye, buster, jessie, jessie-kfreebsd, sid, stretch
  • size: 160 kB
  • ctags: 85
  • sloc: perl: 941; makefile: 7
file content (36 lines) | stat: -rw-r--r-- 1,368 bytes parent folder | download
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
Source: libtest-tabledriven-perl
Section: perl
Priority: optional
Build-Depends: cdbs,
 devscripts,
 perl,
 debhelper,
 dh-buildinfo
Maintainer: Debian Perl Group <pkg-perl-maintainers@lists.alioth.debian.org>
Uploaders: Jonas Smedegaard <dr@jones.dk>
Standards-Version: 3.9.4
Vcs-Git: git://anonscm.debian.org/git/pkg-perl/packages/libtest-tabledriven-perl
Vcs-Browser: http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/libtest-tabledriven-perl.git
Homepage: http://search.cpan.org/dist/Test-TableDriven/

Package: libtest-tabledriven-perl
Architecture: all
Depends: ${cdbs:Depends},
 ${misc:Depends},
 ${perl:Depends}
Recommends: ${cdbs:Recommends}
Suggests: ${cdbs:Suggests}
Description: write tests, not scripts that run them
 Writing table-driven tests is usually a good idea.  Adding a test case
 doesn't require adding code, so it's easy to avoid fucking up the
 other tests.  However, actually going from a table of tests to a test
 that runs is non-trivial.
 .
 Test::TableDriven makes writing the test drivers trivial.  You simply
 define your test cases and write a function that turns the input data
 into output data to compare against.  C<Test::TableDriven> will compute
 how many tests need to be run, and then run the tests.
 .
 Concentrate on your data and what you're testing, not
  plan tests => scalar keys %test_cases
 and a big foreach loop.