I work on expanding Test::MockDBI
to address some of its
limitations (e.g. support for fetchrow_hashref
and control of
, see also a cpanratings review
It uses a test setup where test programs are
generated on the fly.
The motivation for doing so is noted in the HISTORY
- The separate test programs are autogenerated so they use
the correct #! startup line.
It works like this:
It strikes me as unnecessarily complex. If I were to expand the
module, do you think I should continue using the same approach?
No matter how great and destructive your problems may seem now, remember, you've probably only seen the tip of them.