Do you mean for our own testing or for end users?

For our own tests (DbFit.AcceptanceTests), I think that's a good idea and we should do it. 

For these particular tests, I planned to make them as simple as possible, since they would be the first thing new users see. My feeling is that a properties-based connection adds unnecessary indirection (the new user has to root around on the file system). I'd prefer to leave it as is.

I could:
* add links to the docs where alternative connection mechanisms are described
* not include these tests in the acceptance test suite

Thoughts?