You could also do the same with the whole test script if you haven't been configured got a valid config file.

The skip reason could be a pointer to the README, describing how to configure the tests.

Alternatively, if you do want to access a live db which hasn't been explicitly configured in, then please make sure you use table names which are very likely not to be in use already.

Actually, if you're going the non-configured route, it might be better to abort your test script if your chosen database already exists at start time, to avoid stomping on any data. Then create/drop it during your script(s).