New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dumper-fuzzy barfs a hairball now and then #483
Comments
https://github.com/dubzzz/fast-check/blob/master/documentation/1-Guides/Tips.md#replay-after-failure is this what you are asking for? |
👍 That should do it for now; I do wonder why the fuzzy test generator only triggers this once in a while, but I guess it's tickling an edge case there, maybe in test generation, maybe in the library itself. |
I think fuzzy data is pseudo-random, and some rare edge case may not happen every time. |
Indeed, it's a game of change every time, but when I filed this issue, the reported test failure (bug) was only happening very rarely, about once every 20 test runs ( I increased the number of fuzzer runs (GerHobbelt@587b02c) not to have a guarantee but merely to increase the likelyhood that any bug triggered by the fuzzer would get reported on a When a weird bug is reported more often it's more likely to be investigated than a fluke that happens rarely -- I know I shouldn't treat error reports like that, but sometimes I was working on something else and then the bug would turn up, but it would quickly scroll off screen and I would have a WTF moment. 😉 Now, at 3000 rounds, I feel more certain that the many edges of js-yaml get tested more thoroughly and will be reported often enough that I will notice them, even when I'm really looking for other things. Let's say I'm trying to mix the human condition with the technical reality of (pseudo)random-driven test suites like 25-dumper-fuzzy. 😄 |
25-dumper-fuzzy.js
sporadically barfs a hairball like the one shown below.Can anyone give a few tips/hints how to track this down without perhaps ripping fast-check open and inspecting the entrails there?
The text was updated successfully, but these errors were encountered: