Skip to content

Ambiguous error with toBeEnabled and negated isNot #1986

@dprevost-LMI

Description

@dprevost-LMI

As shown in the screenshot below, when using negation with a matcher like toBeEnabled (e.g. with enhanceErrorBe), the message is ambiguous with the double not in Expected [not]: "not enabled"
Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workinghelp wantedExtra attention is needed

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions