Skip to content

Hypothesis testing #9

Closed as duplicate
Closed as duplicate

Description

@TomNicholas

Part of the point of splitting up kerchunk to become more modular is so that each component can be rigorously tested. A good way to do that might be to use hypothesis' array testing strategies. I'm not sure quite what this would look like though, because testing round-tripping to disk would be slow, and hypothesis works best when each test is very quick to run.

Activity

  1. maxrjones commented on Mar 10, 2025

    @maxrjones
    Member

    Let's track progress in #394, which provides a more detailed overview of the motivations for property-based testing (e.g., using hypothesis)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions