| 1 |
Source: libtest-tabledriven-perl |
| 2 |
Section: perl |
| 3 |
Priority: optional |
| 4 |
Build-Depends: |
| 5 |
debhelper-compat (= 13), |
| 6 |
libmodule-package-perl, |
| 7 |
Maintainer: Debian Perl Group <[email protected]> |
| 8 |
Uploaders: Jonas Smedegaard <[email protected]> |
| 9 |
Standards-Version: 4.7.2 |
| 10 |
Vcs-Git: https://salsa.debian.org/perl-team/modules/packages/libtest-tabledriven-perl.git |
| 11 |
Vcs-Browser: https://salsa.debian.org/perl-team/modules/packages/libtest-tabledriven-perl |
| 12 |
Homepage: https://metacpan.org/release/Test-TableDriven |
| 13 |
Testsuite: autopkgtest-pkg-perl |
| 14 |
|
| 15 |
Package: libtest-tabledriven-perl |
| 16 |
Architecture: all |
| 17 |
Depends: |
| 18 |
${misc:Depends}, |
| 19 |
${perl:Depends} |
| 20 |
Description: write tests, not scripts that run them |
| 21 |
Writing table-driven tests is usually a good idea. Adding a test case |
| 22 |
doesn't require adding code, so it's easy to avoid fucking up the |
| 23 |
other tests. However, actually going from a table of tests to a test |
| 24 |
that runs is non-trivial. |
| 25 |
. |
| 26 |
Test::TableDriven makes writing the test drivers trivial. You simply |
| 27 |
define your test cases and write a function that turns the input data |
| 28 |
into output data to compare against. C<Test::TableDriven> will compute |
| 29 |
how many tests need to be run, and then run the tests. |
| 30 |
. |
| 31 |
Concentrate on your data and what you're testing, not |
| 32 |
plan tests => scalar keys %test_cases |
| 33 |
and a big foreach loop. |
| 34 |
Multi-Arch: foreign |