Open dabd opened 5 years ago
@dabd I haven't dug into the classification code much, so I'll need some time to think about it. Thanks for suggesting this.
@non In your talk about scalacheck you mention in one of the slides that we should pay attention to the distribution and range of generators. It would be useful to have tools to look at test case distribution on par with Haskell's QuickCheck tools such as cover
and similar. checkCoverage
looks useful as a better stopping criteria than choosing an arbitrary minSuccessfulTests
.
When defining multiple classify conditions to collect statistics on a property, the currently available
classify
methods onProp
require nesting eachclassify
call resulting in deeply nested code. A method that accepts a flat list of classify conditions would make it more pleasant to use. Something like (using Stream so we don't evaluate all conditions prematurely):