Content
View differences
Updated by GitHub almost 12 years ago
I found the following problems when comparing [the plan for RSpec 3](http://myronmars.to/n/dev-blog/2013/07/the-plan-for-rspec-3) with our code. This may not be complete.
### Details
- <span style="text-align:left;">[code\>have(x).item</code> matcher removed from core](http://myronmars.to/n/dev-blog/2013/07/the-plan-for-rspec-3#expectations__matchers_will_be_moved_into_an_external_gem)</span>
- include <code>rspec-expactations</code> gem
- remove **18** occurences
<!-- end list -->
- [Use of <code>should</code>, <code>should\_not</code>, and <code>should\_receive</code> raises deprecation warning](http://myronmars.to/n/dev-blog/2013/07/the-plan-for-rspec-3#what_about_the_old_expectationmock_syntax)
- [enable <code>should</code> syntax explicitly](https://www.relishapp.com/rspec/rspec-expectations/docs/syntax-configuration#explicitly-enable-both-syntaxes)
- replace about **3110** occurences of <code>should</code> by <code>expect</code>
<!-- end list -->
- <span style="text-align:left;">[code\>example</code> may not directly usable](http://myronmars.to/n/dev-blog/2013/07/the-plan-for-rspec-3#core_dsl_methods_will_yield_the_example)</span>
- adapt the **2** occurences in <code>spec/spec\_helper.rb</code>
<!-- end list -->
- <span style="text-align:left;">[code\>failure\_message\_for\_should(\_not)</code> will become legacy](http://myronmars.to/n/dev-blog/2013/07/the-plan-for-rspec-3#expectations_matcher_protocol_and_custom_matcher_api_changes)</span>
- ignore this until RSpec 4
- replace **4** occurences by <span style="text-align:left;">[code\>failure\_message(\_when\_negated)</code>](https://github.com/rspec/rspec-expectations/issues/270)</span>
### Details
- <span style="text-align:left;">[code\>have(x).item</code> matcher removed from core](http://myronmars.to/n/dev-blog/2013/07/the-plan-for-rspec-3#expectations__matchers_will_be_moved_into_an_external_gem)</span>
- include <code>rspec-expactations</code> gem
- remove **18** occurences
<!-- end list -->
- [Use of <code>should</code>, <code>should\_not</code>, and <code>should\_receive</code> raises deprecation warning](http://myronmars.to/n/dev-blog/2013/07/the-plan-for-rspec-3#what_about_the_old_expectationmock_syntax)
- [enable <code>should</code> syntax explicitly](https://www.relishapp.com/rspec/rspec-expectations/docs/syntax-configuration#explicitly-enable-both-syntaxes)
- replace about **3110** occurences of <code>should</code> by <code>expect</code>
<!-- end list -->
- <span style="text-align:left;">[code\>example</code> may not directly usable](http://myronmars.to/n/dev-blog/2013/07/the-plan-for-rspec-3#core_dsl_methods_will_yield_the_example)</span>
- adapt the **2** occurences in <code>spec/spec\_helper.rb</code>
<!-- end list -->
- <span style="text-align:left;">[code\>failure\_message\_for\_should(\_not)</code> will become legacy](http://myronmars.to/n/dev-blog/2013/07/the-plan-for-rspec-3#expectations_matcher_protocol_and_custom_matcher_api_changes)</span>
- ignore this until RSpec 4
- replace **4** occurences by <span style="text-align:left;">[code\>failure\_message(\_when\_negated)</code>](https://github.com/rspec/rspec-expectations/issues/270)</span>