Write tests, not scripts that run them

Edit Package perl-Test-TableDriven
http://search.cpan.org/dist/Test-TableDriven

Writing table-driven tests is usually a good idea. Adding a test case
doesn't require adding code, so it's easy to avoid messing 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. "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.

Refresh
Refresh
Source Files
Filename Size Changed
Test-TableDriven-0.02.tar.gz 0000013735 13.4 KB
perl-Test-TableDriven.changes 0000000304 304 Bytes
perl-Test-TableDriven.spec 0000001957 1.91 KB
Latest Revision
Dirk Stoecker's avatar Dirk Stoecker (dstoecker) committed (revision 3)
Comments 0
openSUSE Build Service is sponsored by