There might be a problem with the unit tests in some situations: the database creation depends on the user to have the rights to do it. It might be useful to have a short part talk about using SQLite for those situations, because that won't need those rights. And maybe the code could be made to accept an optional database name from the command line, so the user can explicitely give a database name for testing (of an already existing and empty database).
Typical setups where this is a problem are PostgreSQL on Debian systems: users can be created with or without the right to create databases or the config might prevent access of users to databases that are named differently (the default setup of PostgreSQL does that on Debian if you access over unix sockets).
