@pandeiro we're currently ironing out that duplication on the prompt And a variable will be added to avoid the prompt altogether.

@abtv: Are you using the snapshots?

@malabarba: yes

Which of the two methods described in "ClojureScript usage" did you use?

The first or the second?

Cheers @malabarba @bozhidar - I'm trying to work around it by using a wrapper function that calls cider-connect with the project root dir via projectile

hello all, I'm new here, is there an equivalent to lein test in cider?

@twillis: cider-test-run-tests.

Keep in mind you need to load the tests first

that only runs them for the current namespace, lein test runs the whole test suite.

C-c , runs the command cider-test-run-tests, which is an interactive
compiled Lisp function in `cider-test.el'.

It is bound to C-c ,, <menu-bar> <CIDER> <Test> <Run all tests>.

(cider-test-run-tests SUPPRESS-INFERENCE)

Run all tests for the current Clojure source or test report context.

With a prefix arg SUPPRESS-INFERENCE it will try to run the tests in the
current ns.

@twillis: The docstring you quoted disagrees with what you said.

lol

yeah you are right. but the behavior i'm seeing is it only runs the corresponding tests for whichever buffer i'm in.

as if i'm running it with a prefix arg If i'm reading that doc string right

Hm

you're right, I get the same

@bozhidar: Is this intended?

source confirms....

(defun cider-test-run-tests (suppress-inference)
  "Run all tests for the current Clojure source or test report context.

With a prefix arg SUPPRESS-INFERENCE it will try to run the tests in the
current ns."
  (interactive "P")
  (if-let ((ns (if suppress-inference
                   (clojure-find-ns)
                 (or (funcall cider-test-infer-test-ns (clojure-find-ns))
                     (when (eq major-mode 'cider-test-report-mode)
                       cider-test-last-test-ns)))))
      (cider-test-execute ns nil)
    (message "No namespace to test in current context")))

I actually prefer the behavior the way it is, but I routinely run lein test like a good dev before I push, and was just curious if I could do the equivalent with cider, since it would make it easier to jump to problem areas. I guess if I run it in a compile buffer I get some of that back.

I have my tests running automatically in the background on save so I’ve never used CIDER to do it.

ideally one could just run M-x compile with lein test-refresh but the output doesnt get parsed right to make niceties like jumping to where the error occurred possible

I had some code to make compile play nice with lein

I'll try to look for it later

I planned on adding it directly to Emacs, but the compile.el code is... complicated

there’s no way right now to run all the tests

in the project

I believe this was requested a few times, but we never got to implementing it

there’s also something else to consider

running the tests for all loaded namespaces would be fairly easy

running the tests for all files in the project would require a somewhat different approach compared to the one we use now

I think all loaded namespaces would be a good start

besides, I think if the user has refactor-nrepl set up, then "loaded namespaces" ends up being equal to "all namespaces"

So there's an easy workaround for that limitation

yeah I think C-u C-c C-x loads everything and it's in my muscle memory now

my vote for keybinding is C-C <

hehe

I wouldn’t worry that much about the keybinding

I’m more concerned about finding time to actually implement this

you want me to put a bug in github? feature request style?

nope

https://github.com/clojure-emacs/cider/issues/1226

feel free to add more comments here

ah ok thanks much

@malabarba: Sorry, I didn't mention your question

I'm trying the first option

>Issue M-x customize-variable RET cider-cljs-repl if you'd like to change the REPL used (the default is rhino).

And it shows "no match"

And if I run cider-jack-in-clojurescript it shows an error:

>IllegalArgumentException No value supplied for key: [email protected] clojure.lang.PersistentHashMap.create (PersistentHashMap.java:77)

If I use the second option I can change cider-cljs-repl (I see alternatives there), but it also doesn't work