This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-09-04
Channels
- # announcements (5)
- # aws (12)
- # beginners (76)
- # boot (29)
- # cider (24)
- # circleci (9)
- # clojure (64)
- # clojure-dev (27)
- # clojure-europe (3)
- # clojure-houston (1)
- # clojure-italy (33)
- # clojure-nl (19)
- # clojure-poland (1)
- # clojure-spec (6)
- # clojure-uk (20)
- # clojurescript (103)
- # clojutre (1)
- # code-reviews (60)
- # cursive (76)
- # data-science (20)
- # datomic (20)
- # duct (58)
- # figwheel-main (4)
- # fulcro (36)
- # graphql (6)
- # kaocha (4)
- # onyx (1)
- # pathom (15)
- # quil (3)
- # re-frame (15)
- # reagent (15)
- # reitit (9)
- # remote-jobs (2)
- # rewrite-clj (16)
- # ring-swagger (7)
- # shadow-cljs (132)
- # spacemacs (12)
- # sql (5)
- # vim (9)
- # xtdb (12)
- # yada (4)
i have a function from ::a
-> ::b
and i am testing it with stest/check
. i have set :num-tests
to 1 via: (stest/check 'the-sym {:clojure.spec.test.check/opts {:num-tests 1}})
. does it make sense that i would see two ::a
s generated?
[i've verified that both generated ::a
s are non-trivial/non-empty so it shouldn't be stest
peeking at the first and considering it "not good enough" then proceeding to the second].
hmm... i guess there could be a hidden such-that
or some other "retry" mechanism behind the scenes.
you may see it gen more than once
even in a single test