org.scalatest.prop.PropertyCheckResult
How many generated values passed the property before the failure.
The Exception that was thrown by the property, if any.
TODO: how does this parameter differ 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 extremely valuable while debugging the error: re-running the property with the same seed should retry the test with exactly the same text data, so you can easily test your fixes.
The arguments passed in to this check.
The Exception that was thrown by the property, if any.
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 extremely valuable while debugging the error: re-running the property with the same seed should retry the test with exactly the same text data, so you can easily test your fixes.
TODO: how does this parameter differ from argsPassed?
How many generated values passed the property before the failure.
This Property Check did not succeed -- the property was falsified.
This generally indicates a bug in your code. Values were generated that turned out to produce an error. The next step is usually to examine these values, and understand why they caused an error.
Note that this does not
mean that the code under test is in error: it is possible that the property itself is incorrect. It is good practice to check both, and figure out which one is wrong.necessarily
How many generated values passed the property before the failure.
The Exception that was thrown by the property, if any.
TODO: how does this parameter differ 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 extremely valuable while debugging the error: re-running the property with the same seed should retry the test with exactly the same text data, so you can easily test your fixes.