This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-04-30
Channels
- # announcements (7)
- # beginners (103)
- # boot (62)
- # cider (14)
- # clara (10)
- # cljdoc (4)
- # cljs-dev (2)
- # cljsrn (2)
- # clojure (51)
- # clojure-dev (15)
- # clojure-europe (13)
- # clojure-italy (25)
- # clojure-japan (3)
- # clojure-nl (4)
- # clojure-spec (6)
- # clojure-uk (9)
- # clojurescript (72)
- # clojureverse-ops (2)
- # community-development (2)
- # core-async (35)
- # cursive (16)
- # datascript (1)
- # datomic (12)
- # duct (2)
- # emacs (2)
- # fulcro (9)
- # graphql (5)
- # hoplon (5)
- # leiningen (3)
- # luminus (1)
- # nyc (1)
- # off-topic (41)
- # other-languages (1)
- # pathom (16)
- # pedestal (2)
- # re-frame (44)
- # reitit (1)
- # shadow-cljs (33)
- # spacemacs (12)
- # test-check (9)
- # tools-deps (15)
- # vim (4)
yeah there's a lot of stuff there; the main reason it's confusing is because I was trying to add more useful and easy-to-use information without breaking stuff relying on the old keys
:result
is the worst part, since it has the truthy-or-exception thing going on; that's why I added the :pass?
key, so you can tell with a straightforward check whether the test passed or not
:result-data
is customizable, if you write a property that returns something that satsifies the clojure.test.check.results/Result
protocol
the only specific use of it that's baked in is when a normal property throws an exception, the exception is added as a key in the result-data
which might currently have the unfortunate side effect of causing exceptions to be printed twice 😞
I can see both parts are fairly undocumented 😕
I tried to spec things at some point I think; maybe that'd be a good way to start
Except they probably haven't added docstrings to specs yet have they