Search code examples
javadatabasehibernatejunitdbunit

Handling schema changes when working with multiple feature branches

Is there another way, or some tool, to handle database schema changes in multiple parallel feature branches other than creating a separate database for each one in development?

ie. Spin up a DB in memory based on some configuration or script and populate with DbUnit before running tests.

This question is specifically targeted at unit testing, but could be applicable to UAT as well.

Solution

  • After a long while, it seems like Liquibase, in conjunction with other tools like DbUnit, should be able to accomplish what I had originally asked.

    Thanks for all of the other suggestions.