Skip to content

spirv-fuzz: Strict assertions for testing #3185

@afd

Description

@afd

When checking the precondition of a transformation, there are cases where the transformation is potentially valid but does not apply, and cases where the transformation is completely bogus and should not have been created in the first place.

For the second case, when writing transformation unit tests we would like to be able to have negative tests that check that such transformations are not applicable.

But when actually running the fuzzer, we would like an assertion to fail when a completely invalid transformation is created.

Some thought is required to figure out how best to allow both cases.

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