libtest-tabledriven-perl 0.02-3 source package in Ubuntu

Changelog

libtest-tabledriven-perl (0.02-3) unstable; urgency=medium

  [ Debian Janitor ]
  * Set Testsuite header for perl package.
  * Apply multi-arch hints. + libtest-tabledriven-perl: Add Multi-Arch: foreign.

 -- Jelmer Vernooij <email address hidden>  Thu, 13 Oct 2022 17:42:29 +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 Pocket Published Component Section
Noble release universe misc
Mantic release universe misc
Lunar release universe misc

Builds

Lunar: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
libtest-tabledriven-perl_0.02-3.dsc 2.1 KiB 76c138d325c993253596c05a4f2a83b2f4ddb663d432a37af30496e923cdfbc2
libtest-tabledriven-perl_0.02.orig.tar.gz 13.4 KiB 425878afcf2a14e047caf891b1915e9f5ffb036941609c438e0dfbd1b5b1859a
libtest-tabledriven-perl_0.02-3.debian.tar.xz 3.2 KiB 632d3e41c58b9bb3a75acbf07952bff8a6d312c4c65476feb2d73d0db0cdacc3

Available diffs

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.