0

I am part of a team that works on a SpringBoot application and we use liquibase for maintaining our database changes.

Config data that has to be added/removed/modified goes as part of a change-set.

The problem is that there are no ways of validating any liquibase changes from our end. There has been a couple of occurrences lately where an incorrect config data modification change-set broke a functionality.

Is there a way I can implement a test-case sort of thing for the liquibase change-sets to prevent such things from happening in future. If yes, could you please point me to the right direction as I am completely clueless about how to implement that.

Thanks in advance.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.