This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-08-18
Channels
- # alda (6)
- # architecture (1)
- # bangalore-clj (3)
- # beginners (39)
- # boot (292)
- # braveandtrue (1)
- # cider (7)
- # clara (2)
- # cljs-dev (20)
- # cljsjs (9)
- # cljsrn (42)
- # clojure (127)
- # clojure-chennai (1)
- # clojure-dev (96)
- # clojure-india (1)
- # clojure-russia (175)
- # clojure-spec (56)
- # clojure-uk (11)
- # clojureindia (1)
- # clojurescript (82)
- # core-async (7)
- # cursive (21)
- # data-science (1)
- # datomic (173)
- # funcool (4)
- # hoplon (8)
- # instaparse (1)
- # jobs (7)
- # jobs-discuss (1)
- # jobs-rus (30)
- # lambdaisland (1)
- # lein-figwheel (8)
- # off-topic (5)
- # om (51)
- # onyx (79)
- # other-languages (7)
- # planck (8)
- # re-frame (95)
- # reagent (6)
- # rum (8)
- # specter (4)
- # untangled (54)
- # yada (5)
is there a way to have cider display the failing input when using test.check?
for example, when I define the following property:
(defspec whatever
(prop/for-all [x gen/int]
(= 0 x)))
cider can run it just fine, but when it fails I get only a moderately helpful message:
Fail in whatever
expected: result
actual: false
I believe that test.check stores additional information, such as the minimal failing input, in its results, but cider-nrepl doesn't seem to extract it. Has anyone tried to do so? Is it something that people would be interested in?
I would definitely be interested as I am now checking those errors in the terminal only @sebastianpoeplau
@richiardiandrea I'll try to hack something together 🙂
Let me know if you want me to try it out!
@richiardiandrea I've created https://github.com/clojure-emacs/cider/issues/1825 - will have a try at the implementation...