You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using gentest to test itself seems dodgy, so I'm testing it with Mocha right now with explicit calls to gentest.sample and assertions about the generated values. I think this is fine for what it is, but much more should be tested, including a few higher-order generators that have been left out:
test types.fmap
test types.bind
test types.suchThat
test shrinking of each type
test Property
test Runner
add something to measure test coverage
Also, it might be neat to test gentest by writing properties known to be true about the JavaScript standard library, and properties known to be false for specific inputs (making sure it finds those inputs).
The text was updated successfully, but these errors were encountered:
Hi Dan! While I appreciate the desire to help, I don't maintain this package anymore. You might have better luck contributing to a mature project. Some have contribution guidelines and a list of good first issues, like React.
I would recommend taking a look at another js/ts property based testing library fast-check as it is under active development and not written in haskell in js style or clojurescript.
Using gentest to test itself seems dodgy, so I'm testing it with Mocha right now with explicit calls to
gentest.sample
and assertions about the generated values. I think this is fine for what it is, but much more should be tested, including a few higher-order generators that have been left out:Also, it might be neat to test gentest by writing properties known to be true about the JavaScript standard library, and properties known to be false for specific inputs (making sure it finds those inputs).
The text was updated successfully, but these errors were encountered: