libtest-tabledriven-perl 0.02-4 source package in Ubuntu
Changelog
libtest-tabledriven-perl (0.02-4) unstable; urgency=medium * Team upload. * Remove Makefile.old via debian/clean. (Closes: #1047997) -- gregor herrmann <email address hidden> Thu, 07 Mar 2024 19:30:47 +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 | |
|---|---|---|---|---|
| Oracular | release | universe | misc |
Downloads
| File | Size | SHA-256 Checksum |
|---|---|---|
| libtest-tabledriven-perl_0.02-4.dsc | 2.4 KiB | 3b91374cbc758706b2d0edbae1eed152d045f2018bcbfdfb6094a91e6dd7e7d0 |
| libtest-tabledriven-perl_0.02.orig.tar.gz | 13.4 KiB | 425878afcf2a14e047caf891b1915e9f5ffb036941609c438e0dfbd1b5b1859a |
| libtest-tabledriven-perl_0.02-4.debian.tar.xz | 3.3 KiB | 5de4206c5c68053eb1aab0d0d64d6415968ea6c0c38cfb05959d667c83adda3c |
Available diffs
- diff from 0.02-3 to 0.02-4 (389 bytes)
No changes file available.
Binary packages built by this source
- libtest-tabledriven-perl: 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.
