Clojurians Log v2

Asked a similar question, a boundary (defprotocol) we defined ourselves, but idea is the same I think

So create a test profile I guess with the specific config for test

duct profile

Instead of writing to postgres you write to h2

I think it is a good practice.

You could also setup the environment with a local postgres instance (docker image) and then run integration tests against that. Then mark the tests with (deftest ^:integration and add test-selectors to project.clj

:test-selectors {:unit (complement :integration)
                 :integration :integration}

hello @erwinrooijakkers and @kelveden, thank you very much for your replies that helped me solve my issue. What I did is that : 1. I realized that in [duct/core “0.8.0”] a specific duct.profile/test was introduced (I was using 0.7.0), and upgraded to 0.8.0. This helped me avoid the creation of test lein profile 2. In my config.edn added a line (below the dev profile one) :

:duct.profile/test #duct/include "test.edn"

there is a small issue that caused me a crash in duct.core and this is why I had to introduce the “.edn” extension (https://github.com/duct-framework/core/issues/23)

and then : 3. added in duct_hierarchy.edn the code:

{:my-project.migration/h2 [:my-project.migration/sql]
 :my-project.migration/postgres [:my-project.migration/sql]}

:duct.migrator/ragtime
  {:migrations [#ig/ref :co.ytems.aeolus.migration/sql]}

thanks again for your help ! 👍