Thanks!

[rix0rrr]

Thank you for writing this magnificent library!

Here are two more issues it found for your showcase:

eemeli/yaml#56
eemeli/yaml#57

(Not the project maintainer, don't know how happy he would be to be featured--but he seemed good-natured about it and tools like this deserve more recognition)

[dubzzz]

When I used fast-check on js-yaml, I relied on the following Arbitrary:

// Generate valid YAML instances for yaml.safeDump
var key = fc.fullUnicodeString();
var values = [
		  key, fc.boolean(), fc.integer(), fc.double(),
		  fc.constantFrom(null, Number.NEGATIVE_INFINITY, Number.POSITIVE_INFINITY)
];
var yamlArbitrary = fc.object({ key: key, values: values });

Using it might detect other bugs: unicode encoding, rounding issues... You should give it a try too :)

Thanks a lot for the issues :)
I need to find a better way to reference the bugs detected using fast-check, they are very interesting and prove the need for such tests

[dubzzz]

It might be great to add fast-check tests in the unit tests of the package you referenced :) It should protect the author from adding regressions

[rix0rrr]

I was about to do that, then I noticed the package is a pure JavaScript package.

Do you think fast-check could be utilized without a TS compiler?

[dubzzz]

Yes of course, it can be used in any JavaScript project

See:
https://github.com/nodeca/js-yaml

[dubzzz]

Suggestion of test for the yaml repo: dubzzz/yaml@3a8cb0a

[dubzzz]

Closing the issue, the PR #287 gathers multiple issues discovered with fast-check in a single page