Test::TableDriven - write tests, not scripts that run them River stage one • 5 direct dependents • 8 total dependents

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"...

JROCKWAY/Test-TableDriven-0.02 - 16 Sep 2007 09:29:58 GMT - Search in distribution

1 result (0.032 seconds)