In case of failure: the counterexample contains the minimal failing case (first failure after shrinking)
Since 0.0.7
In case of failure: path to the counterexample
For replay purposes, it can be forced in assert, check, sample and statistics using Parameters
Since 1.0.0
In case of failure: it contains the reason of the failure
Since 0.0.7
In case of failure: it contains the error that has been thrown if any
Since 3.0.0
Execution summary of the run
Traces the origin of each value encountered during the test and its execution status. Can help to diagnose shrinking issues.
You must enable verbose with at least Verbosity.Verbose in Parameters
in order to have values in it:
Since 1.9.0
Does the property failed during the execution of check?
Since 0.0.7
List all failures that have occurred during the run
You must enable verbose with at least Verbosity.Verbose in Parameters
in order to have values in it
Since 1.1.0
Was the execution interrupted?
Since 1.19.0
Number of runs
Since 1.0.0
Number of shrinks required to get to the minimal failing case (aka counterexample)
Since 1.0.0
Number of skipped entries due to failed pre-condition
As numRuns it only takes into account the skipped values that occured before the first failure.
Refer to pre to add such pre-conditions.
Since 1.3.0
Configuration of the run
It includes both local parameters set on check or assert and global ones specified using configureGlobal
Since 1.25.0
Seed that have been used by the run
It can be forced in assert, check, sample and statistics using Parameters
Since 0.0.7
Verbosity level required by the user
Since 1.9.0
Run reported as success
Refer to RunDetailsCommon for more details
Remarks
Since 1.25.0