rspec-expectations
rspec-expectations copied to clipboard
rspec
Provides a readable API to express expected outcomes of a code example
Fixes #1190 Display the actual error message of the raised error when a raise_error assertion fails. The failure message will now include the error message on a separate line followed...
I'm doing: `expect { call }.to raise_error(/ABORTED/)` this triggers a http request and then it ends up as: ``` expected /ABORTED/, got #
This addresses issue #1025. With this change, the `StartWith` matcher will rely on an object's `start_with?` method if available. Similarly, the `EndWith` matcher will rely on an object's `end_with?` method...
### Subject of the issue Was writing some tests in my project, was using match_array to make some expectations and noticed that it causing some tests to never finish. ###...
This is somewhat related to #495, at least in that my use case is using compound matchers against complex objects. I might not need this if diffs are disabled for...
Maybe we can have both strict (true/false) and loose (truthy/falsey) forms of the be/have matchers? That way, regardless of which is the "default", it is easy to do inline adjustment...
This issue is meant to follow the deprecation we will introduce in rspec-expectations 3.99. * Ruby < 2.3 is no longer supported. (Phil Pirozhkov, #1230 * Will be handled by...
I've seen a lot of custom matchers, and ours included, reimplement the same interface of `#once`, `#twice`, `#at_least` etc. Sometimes partially, sometimes completely. A `Countable` module can be used in...
### Subject of the issue This is a feature request. I think it could be a good idea to let people "extend" RSpec matchers with chaining capabilities. For exammple: ```ruby...
The questions about custom differ already appeared in the past in #627, #97. I think it could be valuable to allow custom differ objects in matchers. The proposed solution should...
