Now the AssertionErrors thrown by tests are immediately propagated upwards so they land in standard output, or are captured by unit testing library under which the properties are being tested. This loses information which particular testcase has caused the property to fail.
We shall at least include the values in the exception being thrown; it should likely be a custom exception derived from AssertionError. This way, in case of failed tests we will have both the stacktrace (incl. the offending assert that caused the failure) and values for the test case itself.
Now the
AssertionError
s thrown by tests are immediately propagated upwards so they land in standard output, or are captured by unit testing library under which the properties are being tested. This loses information which particular testcase has caused the property to fail.We shall at least include the values in the exception being thrown; it should likely be a custom exception derived from
AssertionError
. This way, in case of failed tests we will have both the stacktrace (incl. the offendingassert
that caused the failure) and values for the test case itself.