Skip to content

Coverage-guided fuzz testing #10

@pkhuong

Description

@pkhuong

We have some randomised testing with proptest, but we could probably exercise edge cases more reliably with branch coverage information. The main obstable is that allocation classes are immortal and stateful (they remember freed allocations), so we probably want to fork for each call... and rust fuzzers seem to really want to run in persistent mode.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions