Repository navigation
How exactly to rerun failed examples? #281
Description
Activity
You should have the shrunken version of the values that failed your property printed to the console by the failure handler.
Yes. But if you have quite complicated structures (even after shrinking) with very custom
descriptionstrings, it can be very hard to take that output and translate it back to code that initializes said value. This is certainly true in my case.Very true. This is a language-level problem I think, and requires a language-level solution. Being able to stringify arbitrary bits of the AST with a good macro system would make this trivial.
In the mean time, as a hack, you could write a modifier type that dumps a value declaration as its
descriptionI do agree with your suggestion to improve the replay diagnostic. Especially now that Xcode lets you copy diagnostic banner text.
Reacted by Pierpaolo FrasaI do agree with your suggestion to improve the replay diagnostic. Especially now that Xcode lets you copy diagnostic banner text.
Maybe one could also add another property to
CheckerArguments, likerunOnlyExample: Int? Then the output could indicate the seed, the size and also this attribute so the exact test case can be easily reproduced.
Hi, I'm trying to figure out how exactly to reproduce a failure in my test so I can debug it. I receive output like "Replay with 1006624065 8850 and size 2". But I'm not exactly sure how I can generate the exact example that caused the failure.
I'm trying
but it looks like that generates 100 test cases. How can I get only exactly the one that failed?
As a workaround I guess I can assign my condition in the
forAllclosure to a variable and work withif ... else, but maybe there's an easier way.(Also, it would be nice if the output could be something like
or something, because currently it's not really intuitively clear where these values need to be inserted.)