org.scalatest.prop.PropertyCheckResult
How many generated values succeeded.
How many generated values were rejected as not satisfying the property's preconditions.
TODO: how does this parameter different from argsPassed?
The arguments passed in to this check.
The random seed used for this check. This seed is used by the checking code, to pass in to calls to Randomizer. Reusing the same seed for subsequent runs should produce the same results, so this can be valuable debugging information if you are seeing inconsistent results -- this tells you a seed that produced indeterminate results.
The arguments passed in to this check.
How many generated values were rejected as not satisfying the property's preconditions.
The random seed used for this check.
The random seed used for this check. This seed is used by the checking code, to pass in to calls to Randomizer. Reusing the same seed for subsequent runs should produce the same results, so this can be valuable debugging information if you are seeing inconsistent results -- this tells you a seed that produced indeterminate results.
TODO: how does this parameter different from argsPassed?
How many generated values succeeded.
This Property Check was inconclusive -- after running for the desired number of times, so many attempts were discarded that the property as defined should be considered suspect.
Note that this does *not* mean that the check failed. No falsifying examples were found. The problem is that the property rejected so many of the generated parameters that it looks a bit iffy.
TODO: describe how constraints work in this check environment, and precisely how discarding works.
How many generated values succeeded.
How many generated values were rejected as not satisfying the property's preconditions.
TODO: how does this parameter different from argsPassed?
The arguments passed in to this check.
The random seed used for this check. This seed is used by the checking code, to pass in to calls to Randomizer. Reusing the same seed for subsequent runs should produce the same results, so this can be valuable debugging information if you are seeing inconsistent results -- this tells you a seed that produced indeterminate results.