pholser/junit-quickcheck

Support Iterator-like style for shrink implementation

Closed this issue · 2 comments

vlsi commented

Currently shrink causes lots of objects to be created because doShrink should return List.

It guess it would be better if shrinks could be added iteratively, so the verifier could pick objects and verify them. If property still fails, it could try shrinking the object that fails.

I guess it would produce more targeted results while current API does not make it clear how many shrink results should be produced.

@visi Sounds reasonable -- I'll investigate.

vlsi commented

This duplicates #220