Fail property test when discard count exceeds maximumDiscarded
#112
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Property tests with a
maximumDiscarded
value of zero fail without running any tests. This is a bug introduced by the stream refactors in #39.This is because the status stream now outputs an initial empty
Status.start
value which satisfies thediscard <= maximumDiscarded
stop condition.Prior to the refactor, the stream wouldn't output the
Status.start
value, so a single test would be run before the condition was checked. This behaviour was also odd: even if no values were actually discarded, the property test could fail with a discard error.This PR alters the discard behaviour. The discard count must exceed the
maximumDiscarded
value, not be equal to it. This means that if amaximumDiscarded
value of0
is set, then the test will fail if1
value is discarded.