This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-12-31
Channels
- # beginners (57)
- # boot (25)
- # cider (86)
- # cljs-dev (6)
- # clojure (137)
- # clojure-russia (7)
- # clojure-spec (10)
- # clojure-turkiye (1)
- # clojure-uk (47)
- # clojurescript (37)
- # cursive (10)
- # datascript (2)
- # datomic (2)
- # dirac (59)
- # emacs (1)
- # hoplon (46)
- # instaparse (122)
- # om (32)
- # om-next (1)
- # onyx (3)
- # pedestal (2)
- # perun (4)
- # protorepl (6)
- # re-frame (15)
- # reagent (60)
- # rum (4)
- # specter (7)
- # sql (3)
- # untangled (3)
- # yada (4)
wow, so i finally got around to going through this: https://github.com/gigasquid/genetic-programming-spec and now i'm wondering how it could be used for actual testing
for example, in the program i just specced out i originally wanted to actually match the correctness of args and return values, which would have meant a quadratic number of sfdefs
. i had a list of i think 11 types and five functions...so if i'm doing the math right that would have meant 605 different definitions? now i'm thinking it could actually be possible to enumerate that entire testing space if i learned to have the specs generate themselves... something to think about
is there some way to get more info from this error: "Couldn't satisfy such-that predicate” ? the ex-info map is empty
it's um
probably from an s/and
somewhere
test.check master has a mechanism for spec to add more info in this case, but spec would have to be updated as well
it's something rich asked for
yep 😢