This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-04-11
Channels
- # announcements (3)
- # aws (3)
- # babashka (79)
- # beginners (105)
- # calva (10)
- # chlorine-clover (22)
- # clj-kondo (12)
- # cljs-dev (39)
- # clojure (52)
- # clojure-europe (1)
- # clojure-spec (15)
- # clojure-uk (12)
- # clojurescript (47)
- # conjure (93)
- # data-science (1)
- # datomic (10)
- # emacs (6)
- # figwheel-main (14)
- # fulcro (30)
- # instaparse (3)
- # kaocha (2)
- # lambdaisland (3)
- # malli (2)
- # meander (6)
- # off-topic (27)
- # pathom (14)
- # perun (1)
- # reagent (15)
- # shadow-cljs (69)
- # slack-help (2)
- # spacemacs (5)
- # test-check (23)
- # vim (9)
Is there a way to get test-check to continue running a check even if one fails? I'm looking to create a large list of failure values for further analysis. Going to try using with-redefs on results/pass?
. Curious if anyone else has done something like this.
Are you using defspec in particular? Do you want shrunk values or just original failures?
@gfredericks Just quick-check
on a prop/for-all
.
Wouldn't it be pretty easy to run it in a loop then?
Loop over quick-check N times, collecting failures? Would that cover a good amount of surface area if the iterations to failure is small?
You're worried about there being some small likely failure that keeps getting found and obscuring other larger failures?
I'm looking to find holes in my specs, verifying that the hole is correct or the spec is wrong.
So the tc failure doesn't represent an actual bug?
Getting a PBT library to generate distinct failures without iteratively fixing the earlier ones is pretty hard/advanced
Any small failure is likely to be a component of larger failures
Yep that's part of it
You can get it to start at larger sizes if you think that will help
gen/scale
With min
To be more specific about my problem... We have a wrapper around some data pulled from an external API. We query data out using flat maps. Sometimes your query may have no results. This is the "problem". The solution is either: 1) Our generator for the query generated a map that should never be possible. We need to fix the generator (this can be hard) or acknowledge that this case will return no results 2) The external API is missing data for a particular query that should be there. We need to open a support case with the 3rd party, asking them why this is the case and what should be done.