test-check

nberger 2016-11-29T14:04:56.000193Z

I just created a ticket with a patch proposing a refactor to the quick-check loop that includes a clean way to provide feedback during the test run and also to augment/modify the state carried over during the process, making it easy to implement things like early abort, calculating statistics, adding timestamps at different steps of the process, etc. Feel free to give your feedback in http://dev.clojure.org/jira/browse/TCHECK-126

2016-11-29T14:50:07.000195Z

That would be an interesting extension point for users

2016-11-29T14:52:35.000196Z

transducers might have something to do with this

nberger 2016-11-29T16:45:37.000197Z

I'd like to hear more about your transducers idea :)

2016-11-29T17:42:29.000198Z

It might be thwarted by the irregularity of the shrinking phase

2016-11-29T17:43:48.000199Z

But transducers are maybe related in that they separate the sequence processing logic from the orchestration, so that you can do things like swap in async orchestration

2016-11-29T17:44:22.000200Z

It would be cool if parallelism where swappinable too, but I don't think transducers are amenable to that

alexmiller 2016-11-29T18:02:27.000201Z

not currently

2016-11-29T18:21:26.000202Z

I spent a lot of braintime trying to figure out how to do something transducerlike with the test.check shrink-tree but I think it seemed to hard to do while allowing the shrinking algorithm to do whatever it wanted

2016-11-29T18:22:02.000203Z

I forget what problem I was trying to solve exactly; probably just vague performance