Johannes Link

I'd subscribe to @vlsi's request for a testing scenario that would profit. There may be more elegant ways to tackle those. As for implementation feasibility, there are a couple of...

Next implementation problem: If you keep objects around you have to introduce some lifecycle handling, e.g. for resetting the database. My potentially wrong guess is that objects you want to...

`@ForAll` can only be intercepted by providers but a new annotation could be introduced like `@Any`, which would then be handled by an extension/hook. It would automatically not participate in...

I hope the PowerMock community will award you a medal for that!

@gtrefs Thanks. Fixed.

@gtrefs > In general, _jqwik_ supports [integrated shrinking](https://jqwik.net/docs/current/user-guide.html#integrated-shrinking) which ensures that all preconditions used during data generation will also be preserved while shrinking. In addition shrinkers are directly derived from...

Here's the original: ``` prop Measure k t = label (if k ∈ keys t then "present" else "absent") $ label (if t ≡ nil then "empty" else if keys...

Here's the adapted statistics code: ``` String position = bst.isLeaf() ? "empty" : keys.equals(Collections.singletonList(key)) ? "just key" : keys.stream().allMatch(k -> k.compareTo(key) >= 0) ? "at start" : keys.stream().allMatch(k -> k.compareTo(key)

Rather than using exceptions of any kind, having some kind of notification collector as a return or in/out parameter seems more flexible since any exception will stop an engine's discovery...

Currently, there's no strict format for the report. If you just add it to your reports, someone else might pick the idea up.