Skip to content

Test more of gentest #4

@graue

Description

@graue

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).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions