Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Added generated seeds for FuzzRangeNodes #35

Merged
merged 1 commit into from
Jul 25, 2022
Merged

Added generated seeds for FuzzRangeNodes #35

merged 1 commit into from
Jul 25, 2022

Commits on Jul 21, 2022

  1. Added generated seeds for FuzzRangeNodes 

    Reading and extrapolating from https://go.dev/doc/fuzz/, the Fuzz test will only be fully exercized when a single Fuzz test is run explicitly with the -fuzz parameter to go test. When running go test without this, the Fuzz test will be invoked, but only on the seed corpus. As FuzzRangeNodes did not have a seed corpus, then this test is effectively skipped in our presubmits and CI pipeline.

This change adds the generated corpus from running the fuzz test as the seed corpus. This shouldn't change how well the test is covered when the -fuzz parameter is provided, but does mean that the test will be exercised as part of CI. This seems like a win, but maybe it's bonkers to be submitting generated files?
    @mhutchinson
    mhutchinson committed Jul 21, 2022
    Configuration menu
    Copy the full SHA
    17058cd View commit details
    Browse the repository at this point in the history