I want to have a folder “src” and a folder “test” and then run tests via karma. I have specified :source-paths ["src" "test"], but when I run the tests via npx shadow-cljs compile ci && npm run karma (using setup in https://shadow-cljs.github.io/docs/UsersGuide.html#_the_build) it says 0 tests are found. If I move my test file to the “src” folder and I run the command the tests are found. Is there a way to have a separate test folder from where tests are picked up?

do you actually use shadow-cljs.edn to manage your dependencies? or do you use deps.edn or project.clj?

I use shadow-cljs.edn

and the files are properly namespaced and match the regexp? ie. default namespaces ending in -test

yes

the namespace ends in -test, the file with _test

and you did actually restart shadow-cljs after making that change?

I rerun npx shadow-cljs compile ci && npm run karma

maybe I can do a deeper clean?

that doesn't imply restarting

does it say "connected to server"?

yes

then you still have a server instance running with the old settings I guess

aha 🙂

need to restart that

I stopped the server

now it works 🙂

okay thanks!! 😄

swift reply and happy it works

Real quick question: The docs mention that you can set the compiler option :infer-externs to :auto , which will trigger the compiler to warn about possible extern issues. However, in the compiler options section of the docs, it says that infer-externs defaults to true, which also seems to generate warning about possible extern issues. What’s the difference between :auto and true?

My assumption is that :auto maybe does something extra to generate the appropriate externs (given a simple ^js typehint), and true does not. However, I can’t quite tell from the docs if this is a correct assumption.