What do people think of the idea of amending the tests so they don't use CGI::Wiki::TestConfig at all, but simply use an SQLite database, skipping tests if DBD::SQLite isn't available? I've never been entirely happy with database access information hanging around, and the CGI::Wiki tests should catch any inconsistencies between databases - if they don't then they're incomplete.
I'm sort of fed up of having to faff with things when I'm running the OpenGuides tests, you see - if I'm just testing then I shouldn't have to answer questions.
Kake