I'm using test.check to test a live service. Occasionally it gets a 503 from the service and spends hours trying to shrink the input & reproduce the error.
Is there a way to limit the shrinking process to n iterations? Or disable it entirely for some tests? Is there a better approach for using test.check against a live service where transient issues are expected? Should I just retry the actual service call many times before allowing test.check to see it? Thanks, Matt -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
