On second thought, it would be nice to be able to load the same SQL script as for the compile-time tests. Still, integrating with TestKit should not be necessary and would only complicate things. The easiest solution is probably to not make the actual unit test a DBTest or TestkitTest at all, but to write a plain JUnit test that opens its own database connection (using the new `Database.forConfig`) from the same configuration as the compile-time database.