Skip to content

Option that causes verification to fail for uncoverable cover statements #2299

@adpaco-aws

Description

@adpaco-aws

The RFC for cover statements mentioned:

We can consider adding an option that would cause verification to fail if a cover property was unsatisfiable or unreachable, e.g. --fail-uncoverable.

We are now aware that some users want this option.

It'd be great if we could include this option as part of the "more granular expectations" discussed here. Let's say we had a language to describe expectations for regular properties and cover statements. Then, this expectation is essentially that all cover statements are satisfied.

Metadata

Metadata

Assignees

No one assigned

    Labels

    T-UserTag user issues / requests[C] Feature / EnhancementA new feature request or enhancement to an existing feature.[E] User ExperienceAn UX enhancement for an existing feature. Including deprecation of an existing one.

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions