This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-09-28
Channels
- # arachne (2)
- # aws (5)
- # aws-lambda (5)
- # beginners (4)
- # boot (25)
- # cljs-dev (270)
- # cljsjs (1)
- # cljsrn (72)
- # clojars (5)
- # clojure (201)
- # clojure-belgium (5)
- # clojure-brasil (4)
- # clojure-italy (2)
- # clojure-korea (2)
- # clojure-russia (24)
- # clojure-spec (24)
- # clojure-uk (22)
- # clojurebridge (1)
- # clojurescript (125)
- # cloverage (3)
- # cursive (41)
- # datomic (37)
- # dirac (4)
- # emacs (2)
- # hoplon (421)
- # lein-figwheel (1)
- # leiningen (5)
- # luminus (2)
- # mount (1)
- # off-topic (18)
- # om (44)
- # om-next (4)
- # onyx (44)
- # pedestal (3)
- # proton (9)
- # re-frame (21)
- # reagent (21)
- # ring-swagger (12)
- # specter (9)
- # sql (2)
- # untangled (62)
- # vim (16)
Is there a way to get test errors in the repl, not just the report at the end?
I mean the error generated by the is function.
hm, it is using normal println by default, so it should work, and you don’t see them at all or they all get printed at once at the end with report summary?
I’m just playing with some nREPL stuff for Dirac, so I thought I could give at least some help in case of nREPL
I have it configured as run nrepl with leiningen
I see the end report summary of how many errors and failures there were
And I can also see things I print.
But not the error reports from the test macros.
The test functions do get marked as failed and the failed badge has that output, but a 50 line tool tip is hard to read.
BTW, I just con be two devs to Cursive at work (Credit Suisse) and we are thinking of standardizing in Cursive for pair programming.
Does run test in the repl still work?
I don't know.
I assumed it runs that lein command, connects to nrepl and then runs all tests using cljs.test
I thought it was nrepl magic.
I think it's not a bug, it's a feature.
anyways, if your own println works, you can define your own cljs.test :reporter and implement your own printing to work around this issue I guess
I think that output is hidden on purpose.
And having badges next to each assertion telling you which one passed and which one failed is great.
Yeah... In those screenshot you can see the lack of error output.
and it is for clojure only I assume, I was automatically thinking about cljs, so forget what I wrote 😉
Most people don’t want it cluttering up their REPL if they’re using the GUI functionality
BTW instead of using the tooltip, you can click on the error icon and get a visual diff.
Cursive basically uses clojure.test functionality, but it hooks the test reporting to get the information it needs for the icons etc.
In my team some people would like to get the output anyway
Something that I think can help a lot would be for the window with the diff, which I think is great, to be a proper top level window.
In Windows it cannot be maximized
@pupeno I think you can always re-hook the test reporting and do whatever you want there, e.g call cursive and then print your own thing
@pupeno I'm sure you know this, but if you want to just run the test in the repl and get the output sans cursive you can do (clojure.test/run-tests your-test-ns.t-test)
bfabry not using the keymap is too high of a price to pay though.