clone a postgresql database for testing cleanlyMarch 28th, 2010 by Jeanne Boyarsky
A few “pesky” requirements/constraints
- Multiple developers all over the word have their own local test databases filled with data in different states. The tests must work for everyone. Ideally they won’t leave data floating around either.
- The tests must use PostgreSQL. While the original JForum supported multiple databases, the JavaRanch version has been scaled down to just run with the one we need. We do have some PostgreSQL specific SQL which rules out using an embedded database like HSQLDB or Derby.
- Developers are using both Eclipse and IntelliJ. Tests should care about the IDE anyway, so this isn’t a big constraint.
- Developers are using a variety of operating systems and languages on their operating systems. While code is in English, there can’t be assumptions as to the OS state.
I think the best strategy is to create a second database just for testing. The JForum database would remain untouched and a jforum_integration_test database can be created for the tests. dbUnit can control the state of that special database.
Before I even start thinking about dbUnit, I did a proof of concept to ensure I could create a new database from scratch using the command line. Creating a database is the easy part. The “hard” part is that JForum doesn’t come with a schema. It comes with an installation servlet that creates the schema. While few people will be creating a schema for JForum, the technique I used applies elsewhere.
The procedure “before”
- Start up the JForum war
- Go to the JForum install URL and enter some information which creates the tables
- Run the JavaRanch customizations.
How to clone a database for which you only have a partial script
- Create an empty database
- Arrive at the base schema
- Go the JForum installation URL
- Enter the information to create the tables
- Export the schema thus far
pg_dump -U postgres jforum_integration_test > c:\temp\postgres.sql
- Provide instructions for the rest of the sql which were created by our developers.
How to import
Now for the easy part!
Importing this dump is a matter of a single command:
Lessons learned after
The next day I learned that this wasn’t enough. We also needed some test data from the server. I ran this a few times to get the relevant test data.
My next step will be to actually configure dbUnit against this new database and start writing tests.