This is really good, and I will merge it.

However, I've been thinking about how to improve usability of the connection tables. This documentation will help and is an improvement over what we have now, however I can't help but think that it's a workaround.

Ideally, the table itself would do more validation, kind of like a web form. It'd be great if any exception messages or feedback to the user (in the form of a fixture) could have some examples, or if it could detect what you were trying to do and validate that.

Some examples:

• if jdbc: was detected, it would try to validate the string as a jdbc string
• the classpath could be validated, to make sure that the correct jars are there (and suggest what to do if the wrong jars are in the classpath)

Ideally, the table itself would do more validation, kind of like a web form. It'd be great if any exception messages or feedback to the user (in the form of a fixture) could have some examples, or if it could detect what you were trying to do and validate that.

Yes, error messages could be more self explaining. Though they're usually already quite related to root cause of the problem.
It's best people to start by copy/pasting & following some working example at first place.

Yes, error messages could be more self explaining. Though they're usually already quite related to root cause of the problem.

Connection problems are seem to be the number one topic on the support forums (although I haven't analysed this scientifically) and I think is one of the biggest problems when starting out with DbFit. Examples are good to have but not everyone who is having problems may find them.