Skip to content

Deprecate should_not raise_error in MSpec and replaces usages in ruby/spec #754

Open
@eregon

Description

@eregon

See https://github.com/ruby/spec/pull/753/files#r376792963

should_not raise_error is the same as testing nothing.
Each example already implicitly test no exception is raised.
There might be a few legit cases, but I would expect the vast majority could be removed and replaced with useful expectations actually testing it works as expected.

Currently there are about 176 should_not raise_error in ruby/spec.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions