chose simple, entered my db password and it successfully created and updated the database. Is there anything I am doing wrong or I am meant do?
It is also important to share that there are breaking changes that were introduced especially in v4.13.0, v4.17.0 and 4.23.0 that impacted that I have tried to implement. However still the tests fail. Thanks a lot!
Thanks @mherman22, you must be right! Let me give this a try before I go to bed! Do you have any idea on how to test the database because mvn clean install doesn’t seem to help with database tests.
Have you tried deploying the war file in an openmrs platform sdk instance?
As for running those database tests, Doesn’t running then individually using the IDE capabilities work? Or something like mvn test -Dtest=[testname] -Dsurefire.failIfNoSpecifiedTests=false help?
I see mvn clean install --batch-mode && mvn test -Pskip-default-test -Pintegration-test --batch-mode --file pom.xml in the worlflows. It could work anyway
looks like I am making progress since I am getting different errors now! I am currently getting this error ERROR] Tests run: 18, Failures: 8, Errors: 0, Skipped: 0, Time elapsed: 106.0 s - Pastebin.com. I am following this guide. So I am inquiring, where do I get “all the existing frequencies and dosing units for existing drug orders in the database” on a new installation? Running SELECT DISTINCT frequency FROM drug_order WHERE frequency IS NOT NULL; returns Empty set (0.00 sec). Is there a way to get them on a new installation of OpenMRS or do I have to add them manually? @dkayiwa@mherman22 ?
Then your line of investigation should not be in the direction of where do I get all the existing frequencies and dosing units for existing drug orders in the database” on a new installation?
You must be right! However, thinking through it a little more, if it returns empty changeset, it means no drug orders in the database yet. So I don’t expect it to fail since the test is all about “existing drug order frequencies and units”. Looks like when one upgrades liquibase from 4.13 to 4.14 the error message changes from liquibase.exception.MigrationFailedException: to liquibase.exception.CommandExecutionException: liquibase.exception.LiquibaseException: