Just add it to your :deps or :extra-deps with that version.

It is a lib. So other libs conflicts with it. I cannot control the :deps of the project.

I don't understand what you mean. Can you give a concrete example? With a description of what you can and cannot control.

you control your deps.edn this should be a place where you declare some specific version of some library. and it will take precedence even if another lib in your dependency tree excludes it

To make make the above more concrete with an example. Your deps.edn:

{:deps {lib/a {:mvn/version "1.0.0"}
        lib/b {:mvn/version "0.0.2"}}}

{:deps {lib/b {:mvn/version "0.0.3"}}}

Right. But My goals is the contrary, to forcefully obey

{:deps {lib/b {:mvn/version "0.0.3"}}}

I believe the only reasonable way to do it is to just specify that version manually. But you can have a test that makes sure that it's the right version at all times.

Maybe it gathered all your tests twice? Not sure why exactly - maybe some bug in the runner, maybe something's wrong in your setup.

:test  {:extra-paths ["test"]                                                                  
          :extra-deps  {io.github.cognitect-labs/test-runner                                     
                        {:git/url ""            
                         :sha "9e35c979860c75555adaff7600070c60004a0f44"}}                       
          :main-opts ["-m" "cognitect.test-runner"]                                              
          :exec-fn cognitect.test-runner.api/test}}}

that's in my deps.edn and my minimal tester is just:

ns practice.scratch-test                                                                        
  (:require                                                                                      
    [clojure.test :refer :all]                                                                   
    [practice.scratch :refer :all]))                                                             
                                                                                                 
(deftest a-test                                                                                  
  (testing "add"                                                                                 
    (is (= 0 (add 1 2)))))

did I do something silly there?

the results:

λ ~/projects/clojure/practice : clj -X:test

Running tests in #{"test"}

Testing practice.scratch-test

Testing practice.scratch-test

Ran 2 tests containing 2 assertions.
0 failures, 0 errors.

And no "test" in the :paths in deps.edn?

I just did the same thing (but replaced 0 with 3 and add with +), and my tests ran only once.

I didn't even catch that it wasn't catching the failing test. That is a problem. Hmmm

And no, I have :paths ["src" "resources"] in the deps.edn

My repl connected editor catches that failing test.

Is my deftest form actually correct? I'm coming back to clojure after a little break so was just going off memory there.

Your deftest is correct. But I don't know why it tests the same thing twice and doesn't catch the error. If you can share a minimal reproducible example as a Git repo, I'd take a look.

Will do, give me 1 minute. Thanks!

https://github.com/Chase-Lambert/clojure-practice

You have test/scratch_test.clj with (ns practice.scratch-test ...). And you have test/practice/scratch_test.clj with the same NS. Remove the first one, change the second one (it won't fail otherwise).

accidentily left in a dep for criterium fyi, I just push a commit removing that.

oh my goodness, I left that file in there huh. I told you I was doing something silly! Sorry for wasting your time.

No problem. :)

oh wait, but it's still not catching the failed test (even though it now only runs once of course)

Nope, still being silly, I had changed the test to be successful. Hahaha!

I need more coffee

Thanks again for the assistance