I guess I am missing the point, wouldn't testing the actual functionality of the DB backend and data integrity via the used DBI/DBD and in source SQL be the goal of the DBI related test harness for your application? Doesn't using a fake DB remove one of the possible fail points that actually exists in the application that uses DBI? =) How about a module that replaces your app's subs with
's that output what your harness expects -- seems like another way to simplify your tests. =)