# test-check

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

nberger 16:04:56

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

gfredericks 16:50:07

That would be an interesting extension point for users

gfredericks 16:52:35

transducers might have something to do with this

nberger 18:45:37

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

gfredericks 19:42:29

It might be thwarted by the irregularity of the shrinking phase

gfredericks 19:43:48

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

gfredericks 19:44:22

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

alexmiller 20:02:27

not currently

gfredericks 20:21:26

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

gfredericks 20:22:02

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