We have some integration tests that use configuration from the :test profile. Now I want to run these tests from the REPL (Cider). What's a reasonable way to do it? Ideally, I'd run a single REPL and use :test config values only for tests but I guess there's no easy way how to do it.

@jumar I don’t completely understand the question I think.

What sort of config is in the :test profile?

All sorts of things, mostly 3rd party credentials and database connection config. For me the db connection config is the critical thing I would say - because tests delete all data before they are run.

the tests are intended to use different "test" database

How are you specifying the config though?

I wouldn’t think it’s just arbitrary format in the :test profile

are you using a config lib or something?

We have these config keys in profiles.clj and use environ to read keys from env

Ok

So you should be able to read the environ information in the REPL as well

and it will give you either the env variable, sys property, or whatever is in lein

the :test profile info should be available in a typical lein repl

Right, but I think I'll get only the config values associated with active profile which normally, in my case, is :dev. So I guess I need to run another REPL with the :test profile, right?

The problem is that we have the same keys (e.g. db connection string) in both profiles and they have different values depending on which profile is active (`:dev` or :test). I'm just curious what people usually do in this situation.

hah weird

I think you’d have :dev and :test both active

one just merges over the other

No, that's not the case - in my case, :test is run only for lein test (https://github.com/technomancy/leiningen/blob/master/doc/PROFILES.md#task-specific-profiles)

oh, :test isn’t a default woops

[:base :system :user :provided :dev] defaults

and for repl, so is :repl

But the resource I linked mentions this :-D > Please note that putting things in the :test profile is strongly advised against as it can result in tests which can't be run from the repl.

but I’m not sure what you want to do in your case: you want the lein repl to have visibility into both values for the config at the same time?

I’d think you’d just have a single source of this in :dev

Yeah, I'm really not sure. I guess I cannot expect both profiles to work at the same time. I'll need to think how to configure my tests so that they use different database and are still runnable from the REPL

if you used a different config lib, like say juxt/aero, you can have the various config under :profiles

and you can just use juxt/aero fn to load the config for the profile you want from the repl

but then again, that is changing more stuff and you may be happy with environ

Oh, great. I guess, I won't be able to change config lib now, but that's good to know. Thanks!