Could this be a Cursive related issue? http://stackoverflow.com/questions/36735665/why-do-i-get-this-clojure-exception-cant-change-establish-root-binding-of-u

@cfleming: Thanks for the answer on my 'autocomplete from the REPL' question

I have another one, I write a lot of tests, and Cursive is pretty good on showing where things go awry

It doesn't show the tests properly when they happen in a function (the is in the function gets green'd but not the call in the deftest)

I worked around it by using macros instead of functions, that worked until I got exceptions.

It looks like if I run:

(deftest T
   ...
   (is (some-code-that-may-throw))
   ...)

The error will bubble up to the deftest, I lose all the information about where the issue happened. It makes complex tests a pain to debug.

It looks like the (do-report {:type :error ...}) in the is macro, messes up Cursive test marking, is it intended?

@lsenta: You’re looking for https://github.com/cursive-ide/cursive/issues/823 - I have it about half implemented, it won’t be in the next release but probably the one after that.

That part I solved with macros @cfleming

My issue is that when an exception is triggered in an is, doing (is (exists? "some selenium end-to-end testing selector")) for example, the gutter won't show the line

Instead the whole test will be red and the exception will be shown in the deftest

I rewrote is to do-report a type :fail instead of type :error and it behave in a more useful way