Could be that the complication of testing both SQL and SGLlite means that the support needs to be in separate modules.

I wouldn't be comfortable testing with the user's database even if the user supplies the database name. Could be the users base is misconfigured or the user doesn't recognize the risk. If the user is installing your code on his system I don't see any extra imposition in installing a temporary db.