in reply to
A question of test complexity
First off, why support Test::MockDBI when DBD::Mock exists? The maintainer of that module would love some help, as he's told me more than once.
That method of generating tests is completely outdated and should be rewritten completely. It's unnecessarily complex and doesn't play well with Test::Harness. Put everything into .t files and get rid of the multiple invocations. For one thing, being able to say "prove t/foo.t" is nice.
My criteria for good software:
- Does it work?
- Can someone else come in, make a change, and be reasonably certain no bugs were introduced?