`with-profile test` isn't on by default

[AlexanderMann]

Motivation

I got thrown for a loop when with-profile test wasn't being used by default.

https://circleci.com/gh/circleci/service-utils/48

Suggested Musical Pairing

https://www.youtube.com/watch?v=W3q8Od5qJio

[technomancy]

The docs for Leiningen now specifically advise against using the test profile, but it wouldn't hurt to add a line or two explaining the gotcha in the readme here.

[leblowl]

@technomancy are you referring to this statement:

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.

?

I can see the benefit for having more portable tests. Do you have any ideas on how to handle test specific configuration? That's what I was thinking of using the test profile for. Any thoughts? Thanks

brainstorm attempt 1:

• use a global fixture to change my project's resource-paths temporarily or inject a new test specific configuration state if using component or mount.

[technomancy]

@leblowl right... I think there are ways to do this that are reasonable and don't involve Leiningen profiles.

I don't think it's a good idea to have a separate config for tests vs repl stuff, but if you really decide you want it then you can find a way to make it work with fixtures or some other mechanism. Describing how this would work is out of scope though, because it heavily depends upon how your application is configured.

[leblowl]

Interesting idea about using the same config for repl and testing. I'll think about that. I agree on the scope. Thanks

…

On Mon, Jun 4, 2018 at 12:33 PM, Phil Hagelberg ***@***.***> wrote: @leblowl <https://github.com/leblowl> right... I think there are ways to do this that are reasonable and don't involve Leiningen profiles. I don't think it's a good idea to have a separate config for tests vs repl stuff, but if you really decide you want it then you can find a way to make it work with fixtures or some other mechanism. Describing how this would work is out of scope though, because it heavily depends upon how your application is configured. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#13 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AD2siJmpQPBxYjTjcE8ksjGPV2iBx7vEks5t5X2UgaJpZM4OCx-J> .

-- Lucas Leblow 925-276-2056