Skip to content

Add explicit failure on [not_]to_contain when comparing objects #1247

@jgebal

Description

@jgebal

The contain matcher doesn't handle Oracle Object Type as the check can be only executed on collections and cursors.
We should have add error handling to assure that matcher provides an informative error message.

Something like:
The contain matcher cannot be used to compare Oracle Object Types

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions