Skip to content

Conversation

rl-mike
Copy link

@rl-mike rl-mike commented Mar 7, 2016

The one expectation per example rule should be relaxed.

Even RSpec doesn't apply that limitation on itself. Random example from rspec-expectations.

Better is to recommend that expectations be focused on the goal of the example and/or the test destructured to break down the goal of the expectations.

drujensen and others added 2 commits March 7, 2016 11:28
Remove deprecated error_on method
Even RSpec doesn't apply that limitation on itself.

Better is to recommend that expectations be focused on the goal
of the example and/or the test destructured to break down the goal
of the expectations.
@AlexTalashkevich
Copy link

I would suggest adding an example of using aggregate_failures instead. See http://rspec.info/blog/2015/06/rspec-3-3-has-been-released/ and search for aggregate_failures

pirj added a commit that referenced this pull request Oct 25, 2018
With the [introduction of `aggregate_failures` feature in RSpec 3.3](http://rspec.info/blog/2015/06/rspec-3-3-has-been-released/)
there are no strong arguments left to stick to the strict style, as the
output remains the same, while context initialization costs are reduced.

Closes #11
pirj added a commit that referenced this pull request Oct 25, 2018
With the [introduction of `aggregate_failures` feature in RSpec 3.3](http://rspec.info/blog/2015/06/rspec-3-3-has-been-released/)
there are no strong arguments left to stick to the strict style, as the
output remains the same, while context initialization costs are reduced.

Closes #11
@bbatsov bbatsov closed this in d154ff9 Oct 25, 2018
@pirj pirj deleted the sometimes_two_is_better_than_one branch October 29, 2018 21:07
@pirj
Copy link
Member

pirj commented Oct 31, 2018

Thanks for your input guys!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants