This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-01-29
Channels
- # announcements (8)
- # aws (34)
- # beginners (92)
- # calva (19)
- # capetown (1)
- # cider (10)
- # cljs-dev (7)
- # cljsrn (11)
- # clojars (7)
- # clojure (130)
- # clojure-europe (4)
- # clojure-italy (4)
- # clojure-losangeles (1)
- # clojure-nl (11)
- # clojure-russia (1)
- # clojure-spec (4)
- # clojure-uk (64)
- # clojurescript (51)
- # cursive (9)
- # data-science (6)
- # datomic (29)
- # emacs (3)
- # figwheel-main (14)
- # fulcro (4)
- # graphql (3)
- # jackdaw (2)
- # jobs (4)
- # kaocha (17)
- # leiningen (3)
- # luminus (1)
- # off-topic (46)
- # pedestal (6)
- # portkey (2)
- # re-frame (6)
- # reagent (1)
- # reitit (9)
- # shadow-cljs (9)
- # sql (10)
- # yada (6)
If anyone saw the questions about the repl window posted here just a minute ago, please report to me and I can zap your memory. You didn't see that, just yet. 😃
I'm migrating from midje
to clojure.test
and I'm experiencing a problem on running my tests on vscode
when I Run all tests
it only loads the tests in namespaces that I loaded. Is there a way to load all files in order to be able to run all tests?
What worked so far was running refresh-all
(from clojure.tools.namespace.repl
) and then Run all tests
on a similar note (but I guess you already know that): Run all tests
can't find tests in files that don't match .*test
but Run tests from current namespace
works
I think refresh-all
is the best you can do for now. But please report it so that we have a handle to it when we fix it so that Calva does it for you when you run all tests.

@claynon yeah that only testing ns's ending in -test
has been addressed in git I think, silly bug introduced by me 🙂
I think it's possible that cider invokes the nREPL refresh-all
op before tests, I will examine it's behaviour and do whatever it does to ensure the tests are loaded first 🙂
cider has recently changed a lot of how it's test runner works, so I need to look at what's changed
Couldn't this test runner be part of nrepl (or one of the many orchard projects)? Because running tests is a pretty standard feature in an editor and the output of it seems to be standardized and extensible
I think @claynon was using the fixed version, @mseddon . At least that's how i interpret the report.
We are using nrepl for running the tests, btw. Not sure if that was the suggestion, but anyway 😀
Btw, I have forgotten to tell about it here, maybe... The latest Calva on the marketplace is now using the new repl client.
