You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to use liquibase-test-harness as test tool for liquibase changesets. The problem is, that using tool as is requires to prepare database to pass tests from dependency.
Currently I'm repacking maven jar to exclude dependency resources and leave only compiled classes to be able to run harness framework with empty database.
Is there another option to exclude mandatory base tests, coming from project dependency?
The text was updated successfully, but these errors were encountered:
Hi @snemets thanks for reaching us.
There isn't direct way, but i can think of some workarounds.
We provide init scripts for different DB platforms in src/test/resources/docker folder, maybe you can use them to manually prepare DB.
Some of Liquibase changeObjects require metadata about DB objects (like tables, sequences, etc) already present in DB to be able to manipulate them, so we had to prepare Dbs with init script.
Also you can just fork repo and remove everything you don't need - like input changeLog files and put ones you need instead.
Then run your own version form IDE or CMD, or build your own jar with mvn package. This is beauty of open source )
Hope that helps
I'm trying to use liquibase-test-harness as test tool for liquibase changesets. The problem is, that using tool as is requires to prepare database to pass tests from dependency.
Currently I'm repacking maven jar to exclude dependency resources and leave only compiled classes to be able to run harness framework with empty database.
Is there another option to exclude mandatory base tests, coming from project dependency?
The text was updated successfully, but these errors were encountered: