transpec 1.3.1 → 1.4.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 29b2afb0177a9182376cf1fe10ccad655e4a7e28
-  data.tar.gz: ee45a039ab40a88854a40261ba404de382b2c4d6
+  metadata.gz: f3bc90b69deb7ecd6c16aad1ea76d165efafe220
+  data.tar.gz: 27ea84e9492410a212bd0bf12f24d05ac6c578d0
 SHA512:
-  metadata.gz: 68a1b5c461ccec59168513e353475d1ddf86bae5874fb6adfb426167d7baf67522243d8109b9dd5e6cfa1ed839a5289f06aeef3a6d99947587ad2259c96398d0
-  data.tar.gz: ae2da5b9488b7fd0b1a9b6199e40dbb799211ce0118aec80cd5484e3e2200e0ffabcc2849b531a87c2b69843ac8df00f2830c4eb89cdfc8d0186f1f8186dd1c5
+  metadata.gz: a84904de40d64efeacd01ea3b987e7be6ba3ec684cd6c3c583b582ff85af474d9ee10a3b194b201aebe91b172a6cfa9ce141b3d2d04b9e2753485f72765f512c
+  data.tar.gz: 65b09567e243ee63bf39b2a35d3ce068e5573c5328e62bfe20f757b098fdc856eae83938355ae8eb980a0593b792a1c9d974c942151afe64fdd6ab3ecfeac232

data/.rubocop.yml

@@ -57,4 +57,4 @@ BracesAroundHashParameters:
 
 # TODO: Shorten to 100.
 ClassLength:
-  Max: 150
+  Max: 152

data/.travis.yml

@@ -3,6 +3,4 @@ rvm:
   - 1.9.3
   - 2.0.0
   - jruby-19mode
-script:
-  - bundle exec rake
-  - bundle exec rake test:all
+script: bundle exec rake spec style readme test:all

data/CHANGELOG.md

@@ -2,6 +2,15 @@
 
 ## Development
 
+## v1.4.0
+
+* Support conversion of `RSpec::Core::ExampleGroup#example` ([#23](https://github.com/yujinakayama/transpec/issues/23))
+* Support conversion of one-liner syntax ([#25](https://github.com/yujinakayama/transpec/issues/25))
+* Support conversion of one-liner syntax with `have(n).items` matcher
+* Support conversion of `stub_chain`
+* Fix a bug where `-p/--no-parentheses-matcher-arg` was not applied to the conversion of `have(n).items` with `expect`
+* Fix a bug where conversion summaries of `have(n).item` with negative expectation were reported as positive expectations
+
 ## v1.3.1
 
 * Proceed to conversion even if `rspec` didn't pass in dynamic analysis

data/README.md

@@ -2,7 +2,7 @@
 
 # Transpec
 
-**Transpec** automatically converts your specs into the latest [RSpec](http://rspec.info/) syntax with static and dynamic code analysis.
+**Transpec** automatically converts your specs to the latest [RSpec](http://rspec.info/) syntax with static and dynamic code analysis.
 
 This aims to facilitate smooth transition to RSpec 3, and it's now ready for RSpec 2.99 and 3.0 beta!
 
@@ -184,7 +184,7 @@ Skip dynamic analysis and convert with only static analysis. Note that specifyin
 
 Specify command to run RSpec that is used for dynamic analysis.
 
-Transpec needs to run your specs in copied project directory for dynamic analysis.
+Transpec needs to run your specs in a copied project directory for dynamic analysis.
 If your project requires some special setup or commands to run specs, use this option.
 `bundle exec rspec` is used by default.
 
@@ -216,6 +216,7 @@ $ transpec --keep should_receive,stub
 Type             | Target Syntax                    | Converted Syntax
 -----------------|----------------------------------|-----------------------------------
 `should`         | `obj.should matcher`             | `expect(obj).to matcher`
+`oneliner`       | `it { should ... }`              | `it { is_expected.to ... }`
 `should_receive` | `obj.should_receive`             | `expect(obj).to receive`
 `stub`           | `obj.stub`                       | `allow(obj).to receive`
 `have_items`     | `expect(obj).to have(x).items`   | `expect(obj.size).to eq(x)`
@@ -236,7 +237,7 @@ $ transpec --negative-form to_not
 
 ### `-b/--boolean-matcher`
 
-Specify matcher type that `be_true` and `be_false` will be converted to.
+Specify a matcher type that `be_true` and `be_false` will be converted to.
 Any of `truthy,falsey`, `truthy,falsy` or `true,false` can be specified.
 `truthy,falsey` is used by default.
 
@@ -248,7 +249,7 @@ See [Supported Conversions - Boolean matchers](#boolean-matchers) for more detai
 
 ### `-p/--no-parentheses-matcher-arg`
 
-Suppress parenthesizing argument of matcher when converting
+Suppress parenthesizing arguments of matchers when converting
 `should` with operator matcher to `expect` with non-operator matcher
 (the `expect` syntax does not directly support the operator matchers).
 Note that it will be parenthesized even if this option is specified
@@ -297,7 +298,7 @@ Cannot convert #should into #expect since #expect is not available in the contex
 spec/awesome_spec.rb:4:      1.should == 1
 ```
 
-This message would be shown with specs like this:
+This message would be shown with specs like:
 
 ```ruby
 describe '#should that cannot be converted to #expect' do
@@ -357,6 +358,31 @@ expect(obj).to_not matcher # with `--negative-form to_not`
 * Deprecation: Deprecated since RSpec 3.0
 * See also: [Myron Marston » RSpec's New Expectation Syntax](http://myronmars.to/n/dev-blog/2012/06/rspecs-new-expectation-syntax)
 
+### One-liner expectations
+
+**This conversion is available only if your project has `rspec` gem dependency `2.99.0.beta2` or later.**
+
+```ruby
+# Targets
+it { should matcher }
+it { should_not matcher }
+
+# Converted
+it { is_expected.to matcher }
+it { is_expected.not_to matcher }
+it { is_expected.to_not matcher } # with `--negative-form to_not`
+```
+
+`is_expected.to` is designed for the consistency with the `expect` syntax.
+However the one-liner `should` is still _not_ deprecated in RSpec 3.0
+and available even if the `should` syntax is disabled in `RSpec.configure`.
+So if you think `is_expected.to` is verbose,
+feel free to disable this conversion and continue using the one-liner `should`.
+
+* Conversion can be disabled by: `--keep oneliner`
+* Deprecation: Not deprecated
+* See also: [Add `is_expected` for expect-based one-liner syntax. by myronmarston · rspec/rspec-core](https://github.com/rspec/rspec-core/pull/1180)
+
 ### Operator matchers
 
 ```ruby
@@ -375,13 +401,13 @@ expect('string').to match(/^str/)
 expect([1, 2, 3]).to match_array([2, 1, 3])
 ```
 
-This conversion is combined with the conversion of [Standard expectations](#standard-expecatations) and cannot be disabled separately because the `expect` syntax does not directly support the operator matchers.
+This conversion is combined with the conversion of [standard expectations](#standard-expecatations) and cannot be disabled separately because the `expect` syntax does not directly support the operator matchers.
 
 * See also: [(Almost) All Matchers Are Supported - RSpec's New Expectation Syntax](http://myronmars.to/n/dev-blog/2012/06/rspecs-new-expectation-syntax#almost_all_matchers_are_supported)
 
 ### Boolean matchers
 
-**This conversion is available only if your project has `rspec` gem dependency `2.99` or later.**
+**This conversion is available only if your project has `rspec` gem dependency `2.99.0.beta1` or later.**
 
 ```ruby
 # Targets
@@ -412,7 +438,7 @@ So, converting `be_true`/`be_false` to `be_truthy`/`be_falsey` never breaks your
 ---
 
 * Conversion can be disabled by: `--keep deprecated`
-* Deprecation: Deprecated since RSpec 2.99, removed at RSpec 3.0
+* Deprecation: Deprecated since RSpec 2.99, removed in RSpec 3.0
 * See also: [Consider renaming `be_true` and `be_false` to `be_truthy` and `be_falsey` · rspec/rspec-expectations](https://github.com/rspec/rspec-expectations/issues/283)
 
 ### `be_close` matcher
@@ -426,7 +452,7 @@ expect(1.0 / 3.0).to be_within(0.001).of(0.333)
 ```
 
 * Conversion can be disabled by: `--keep deprecated`
-* Deprecation: Deprecated since RSpec 2.1, removed at RSpec 3.0
+* Deprecation: Deprecated since RSpec 2.1, removed in RSpec 3.0
 * See also: [New be within matcher and RSpec.deprecate fix · rspec/rspec-expectations](https://github.com/rspec/rspec-expectations/pull/32)
 
 ### `have(n).items` matcher
@@ -459,7 +485,7 @@ expect(team.players.size).to eq(3)
 expect(team.send(:players).size).to eq(3)
 ```
 
-There's an option to continue using `have(n).items` matcher with [rspec-collection_matchers](https://github.com/rspec/rspec-collection_matchers) that is an external gem extracted from `rspec-expectations`.
+There's an option to continue using `have(n).items` matcher with [rspec-collection_matchers](https://github.com/rspec/rspec-collection_matchers) that is a gem extracted from `rspec-expectations`.
 If you choose so, disable this conversion by either:
 
 * Specify `--keep have_items` option manually.
@@ -470,9 +496,35 @@ Note: `rspec-rails` 3.0 [still uses `have(n).items` matcher with `rspec-collecti
 ---
 
 * Conversion can be disabled by: `--keep have_items`
-* Deprecation: Deprecated since RSpec 2.99, removed at RSpec 3.0
+* Deprecation: Deprecated since RSpec 2.99, removed in RSpec 3.0
 * See also: [Expectations: have(x).items matchers will be moved into an external gem - The Plan for RSpec 3](http://myronmars.to/n/dev-blog/2013/07/the-plan-for-rspec-3#expectations__matchers_will_be_moved_into_an_external_gem)
 
+### One-liner expectations with `have(n).items` matcher
+
+**This conversion will be disabled automatically if `rspec-collection_matchers` or `rspec-rails` is loaded in your spec.**
+
+```ruby
+# Targets
+it { should have(3).items }
+it { should have_at_least(3).players }
+
+# Converted
+it 'has 3 items' do
+  expect(subject.size).to eq(3)
+end
+
+# With `--keep should`
+it 'has 3 items' do
+  subject.size.should == 3
+end
+
+it 'has at least 3 players' do
+  expect(subject.players.size).to be >= 3
+end
+```
+
+* Conversion can be disabled by: `--keep have_items`
+
 ### Expectations on block
 
 ```ruby
@@ -504,7 +556,7 @@ lambda { do_something }.should_not raise_error # with `--keep should`
 ```
 
 * Conversion can be disabled by: `--keep deprecated`
-* Deprecation: Deprecated since RSpec 2.14, removed at RSpec 3.0
+* Deprecation: Deprecated since RSpec 2.14, removed in RSpec 3.0
 * See also: [Consider deprecating `expect { }.not_to raise_error(SpecificErrorClass)` · rspec/rspec-expectations](https://github.com/rspec/rspec-expectations/issues/231)
 
 ### Message expectations
@@ -542,7 +594,7 @@ Klass.any_instance.stub(:foo) # with `--keep stub`
 ```
 
 * Conversion can be disabled by: `--keep deprecated`
-* Deprecation: Deprecated since RSpec 2.14, removed at RSpec 3.0
+* Deprecation: Deprecated since RSpec 2.14, removed in RSpec 3.0
 * See also: [Don't allow at_least(0) · rspec/rspec-mocks](https://github.com/rspec/rspec-mocks/issues/133)
 
 ### Method stubs
@@ -550,29 +602,38 @@ Klass.any_instance.stub(:foo) # with `--keep stub`
 ```ruby
 # Targets
 obj.stub(:foo)
-
 obj.stub!(:foo)
 
 obj.stub(:foo => 1, :bar => 2)
 
+obj.stub_chain(:foo, :bar, :baz)
+
 Klass.any_instance.stub(:foo)
 
 # Converted
 allow(obj).to receive(:foo)
 
-allow(obj).to receive(:foo)
-
-# If the target project's rspec gem dependency is prior to 3.0
+# If the target project's rspec gem dependency is prior to 3.0.0.beta1
 allow(obj).to receive(:foo).and_return(1)
 allow(obj).to receive(:bar).and_return(2)
 
-# If the target project's rspec gem dependency is 3.0 or later
+# If the target project's rspec gem dependency is 3.0.0.beta1 or later
 allow(obj).to receive_messages(:foo => 1, :bar => 2)
 
+# Conversion from `stub_chain` to `receive_message_chain` is available
+# only if the target project's rspec gem dependency is 2.99.0.beta2 or later
+allow(obj).to receive_message_chain(:foo, :bar, :baz)
+
 allow_any_instance_of(Klass).to receive(:foo)
 ```
 
-Note: `allow(obj).to receive_messages(:foo => 1, :bar => 2)` that is designed to be the replacement for `obj.stub(:foo => 1, :bar => 2)` is available from RSpec 3.0 (though [it's now being considered to be backported to RSpec 2.99](https://github.com/rspec/rspec-mocks/issues/454)). So, in [the upgrade path to RSpec 3](http://myronmars.to/n/dev-blog/2013/07/the-plan-for-rspec-3#the_upgrade_path), if you want to convert them with keeping the syntax correspondence, you need to follow these steps:
+#### No replacement for `unstub`
+
+There's no replacement for `unstub` in the `expect` syntax. See [the discussion](https://github.com/rspec/rspec-mocks/issues/153#issuecomment-12208638) for more details.
+
+#### Steps to upgrade `obj.stub(:foo => 1, :bar => 2)`
+
+`allow(obj).to receive_messages(:foo => 1, :bar => 2)` that is designed to be the replacement for `obj.stub(:foo => 1, :bar => 2)` is available from RSpec 3.0 (though [it's now being considered to be backported to RSpec 2.99](https://github.com/rspec/rspec-mocks/issues/454)). So, in [the upgrade path to RSpec 3](http://myronmars.to/n/dev-blog/2013/07/the-plan-for-rspec-3#the_upgrade_path), if you want to convert them with keeping the syntax correspondence, you need to follow these steps:
 
 1. Upgrade to RSpec 2.99
 2. Run `transpec --keep stub`
@@ -602,7 +663,7 @@ obj.unstub(:foo)
 ```
 
 * Conversion can be disabled by: `--keep deprecated`
-* Deprecation: Deprecated since RSpec 2.14, removed at RSpec 3.0
+* Deprecation: Deprecated since RSpec 2.14, removed in RSpec 3.0
 * See also: [Consider deprecating and/or removing #stub! and #unstub! at some point · rspec/rspec-mocks](https://github.com/rspec/rspec-mocks/issues/122)
 
 ### Method stubs with deprecated specification of number of times
@@ -618,7 +679,7 @@ obj.stub(:foo) # with `--keep stub`
 ```
 
 * Conversion can be disabled by: `--keep deprecated`
-* Deprecation: Deprecated since RSpec 2.14, removed at RSpec 3.0
+* Deprecation: Deprecated since RSpec 2.14, removed in RSpec 3.0
 * See also: [Don't allow at_least(0) · rspec/rspec-mocks](https://github.com/rspec/rspec-mocks/issues/133)
 
 ### Deprecated test double aliases
@@ -633,7 +694,7 @@ double('something')
 ```
 
 * Conversion can be disabled by: `--keep deprecated`
-* Deprecation: Deprecated since RSpec 2.14, removed at RSpec 3.0
+* Deprecation: Deprecated since RSpec 2.14, removed in RSpec 3.0
 * See also: [myronmarston / why_double.md - Gist](https://gist.github.com/myronmarston/6576665)
 
 ### Expectations on attribute of subject with `its`
@@ -673,7 +734,7 @@ describe 'example' do
 end
 ```
 
-There's an option to continue using `its` with [rspec-its](https://github.com/rspec/rspec-its) that is an external gem extracted from `rspec-core`.
+There's an option to continue using `its` with [rspec-its](https://github.com/rspec/rspec-its) that is a gem extracted from `rspec-core`.
 If you choose so, disable this conversion by either:
 
 * Specify `--keep its` option manually.
@@ -682,9 +743,65 @@ If you choose so, disable this conversion by either:
 ---
 
 * Conversion can be disabled by: `--keep its`
-* Deprecation: Deprecated since RSpec 2.99, removed at RSpec 3.0
+* Deprecation: Deprecated since RSpec 2.99, removed in RSpec 3.0
 * See also: [Core: its will be moved into an external gem - The Plan for RSpec 3](http://myronmars.to/n/dev-blog/2013/07/the-plan-for-rspec-3#core__will_be_moved_into_an_external_gem)
 
+### Current example object
+
+**This conversion is available only if your project has `rspec` gem dependency `2.99.0.beta1` or later.**
+
+```ruby
+# Targets
+module ScreenshotHelper
+  def save_failure_screenshot
+    return unless example.exception
+    # ...
+  end
+end
+
+describe 'example page' do
+  include ScreenshotHelper
+  after { save_failure_screenshot }
+  let(:user) { User.find(example.metadata[:user_id]) }
+  # ...
+end
+
+# Converted
+module ScreenshotHelper
+  def save_failure_screenshot
+    return unless RSpec.current_example.exception
+    # ...
+  end
+end
+
+describe 'example page' do
+  include ScreenshotHelper
+  after { save_failure_screenshot }
+  let(:user) { |example| User.find(example.metadata[:user_id]) }
+  # ...
+end
+```
+
+Here's an excerpt from [the warning for `RSpec::Core::ExampleGroup#example` and `#running_example` in RSpec 2.99](https://github.com/rspec/rspec-core/blob/7d6d2ca/lib/rspec/core/example_group.rb#L513-L527):
+
+>`RSpec::Core::ExampleGroup#example` is deprecated and will be removed in RSpec 3. There are a few options for what you can use instead:
+>
+>- `rspec-core`'s DSL methods (`it`, `before`, `after`, `let`, `subject`, etc) now yield the example as a block argument, and that is the recommended way to access the current example from those contexts.
+>- The current example is now exposed via `RSpec.current_example`, which is accessible from any context.
+>- If you can't update the code at this call site (e.g. because it is in an extension gem), you can use this snippet to continue making this method available in RSpec 2.99 and RSpec 3:
+>
+>```ruby
+>RSpec.configure do |c|
+>  c.expose_current_running_example_as :example
+>end
+>```
+
+---
+
+* Conversion can be disabled by: `--keep deprecated`
+* Deprecation: Deprecated since RSpec 2.99, removed in RSpec 3.0
+* See also: [Core: DSL methods will yield the example - The Plan for RSpec 3](http://myronmars.to/n/dev-blog/2013/07/the-plan-for-rspec-3#core_dsl_methods_will_yield_the_example)
+
 ## Compatibility
 
 Tested on MRI 1.9, MRI 2.0 and JRuby in 1.9 mode.

data/README.md.erb

@@ -2,7 +2,7 @@
 
 # Transpec
 
-**Transpec** automatically converts your specs into the latest [RSpec](http://rspec.info/) syntax with static and dynamic code analysis.
+**Transpec** automatically converts your specs to the latest [RSpec](http://rspec.info/) syntax with static and dynamic code analysis.
 
 This aims to facilitate smooth transition to RSpec 3, and it's now ready for RSpec 2.99 and 3.0 beta!
 
@@ -157,7 +157,7 @@ Skip dynamic analysis and convert with only static analysis. Note that specifyin
 
 Specify command to run RSpec that is used for dynamic analysis.
 
-Transpec needs to run your specs in copied project directory for dynamic analysis.
+Transpec needs to run your specs in a copied project directory for dynamic analysis.
 If your project requires some special setup or commands to run specs, use this option.
 `bundle exec rspec` is used by default.
 
@@ -191,6 +191,7 @@ Type             | Target Syntax                    | Converted Syntax
 <%=
 conversion_type_table = <<END
 `should`         | `obj.should matcher`             | `expect(obj).to matcher`
+`oneliner`       | `it { should ... }`              | `it { is_expected.to ... }`
 `should_receive` | `obj.should_receive`             | `expect(obj).to receive`
 `stub`           | `obj.stub`                       | `allow(obj).to receive`
 `have_items`     | `expect(obj).to have(x).items`   | `expect(obj.size).to eq(x)`
@@ -227,7 +228,7 @@ $ transpec --negative-form to_not
 
 ### `-b/--boolean-matcher`
 
-Specify matcher type that `be_true` and `be_false` will be converted to.
+Specify a matcher type that `be_true` and `be_false` will be converted to.
 Any of `truthy,falsey`, `truthy,falsy` or `true,false` can be specified.
 `truthy,falsey` is used by default.
 
@@ -239,7 +240,7 @@ See [Supported Conversions - Boolean matchers](#boolean-matchers) for more detai
 
 ### `-p/--no-parentheses-matcher-arg`
 
-Suppress parenthesizing argument of matcher when converting
+Suppress parenthesizing arguments of matchers when converting
 `should` with operator matcher to `expect` with non-operator matcher
 (the `expect` syntax does not directly support the operator matchers).
 Note that it will be parenthesized even if this option is specified
@@ -293,7 +294,7 @@ Cannot convert #should into #expect since #expect is not available in the contex
 spec/awesome_spec.rb:4:      1.should == 1
 ```
 
-This message would be shown with specs like this:
+This message would be shown with specs like:
 
 ```ruby
 describe '#should that cannot be converted to #expect' do
@@ -353,6 +354,31 @@ expect(obj).to_not matcher # with `--negative-form to_not`
 * Deprecation: Deprecated since RSpec 3.0
 * See also: [Myron Marston » RSpec's New Expectation Syntax](http://myronmars.to/n/dev-blog/2012/06/rspecs-new-expectation-syntax)
 
+### One-liner expectations
+
+**This conversion is available only if your project has `rspec` gem dependency `2.99.0.beta2` or later.**
+
+```ruby
+# Targets
+it { should matcher }
+it { should_not matcher }
+
+# Converted
+it { is_expected.to matcher }
+it { is_expected.not_to matcher }
+it { is_expected.to_not matcher } # with `--negative-form to_not`
+```
+
+`is_expected.to` is designed for the consistency with the `expect` syntax.
+However the one-liner `should` is still _not_ deprecated in RSpec 3.0
+and available even if the `should` syntax is disabled in `RSpec.configure`.
+So if you think `is_expected.to` is verbose,
+feel free to disable this conversion and continue using the one-liner `should`.
+
+* Conversion can be disabled by: `--keep oneliner`
+* Deprecation: Not deprecated
+* See also: [Add `is_expected` for expect-based one-liner syntax. by myronmarston · rspec/rspec-core](https://github.com/rspec/rspec-core/pull/1180)
+
 ### Operator matchers
 
 ```ruby
@@ -371,13 +397,13 @@ expect('string').to match(/^str/)
 expect([1, 2, 3]).to match_array([2, 1, 3])
 ```
 
-This conversion is combined with the conversion of [Standard expectations](#standard-expecatations) and cannot be disabled separately because the `expect` syntax does not directly support the operator matchers.
+This conversion is combined with the conversion of [standard expectations](#standard-expecatations) and cannot be disabled separately because the `expect` syntax does not directly support the operator matchers.
 
 * See also: [(Almost) All Matchers Are Supported - RSpec's New Expectation Syntax](http://myronmars.to/n/dev-blog/2012/06/rspecs-new-expectation-syntax#almost_all_matchers_are_supported)
 
 ### Boolean matchers
 
-**This conversion is available only if your project has `rspec` gem dependency `2.99` or later.**
+**This conversion is available only if your project has `rspec` gem dependency `2.99.0.beta1` or later.**
 
 ```ruby
 # Targets
@@ -408,7 +434,7 @@ So, converting `be_true`/`be_false` to `be_truthy`/`be_falsey` never breaks your
 ---
 
 * Conversion can be disabled by: `--keep deprecated`
-* Deprecation: Deprecated since RSpec 2.99, removed at RSpec 3.0
+* Deprecation: Deprecated since RSpec 2.99, removed in RSpec 3.0
 * See also: [Consider renaming `be_true` and `be_false` to `be_truthy` and `be_falsey` · rspec/rspec-expectations](https://github.com/rspec/rspec-expectations/issues/283)
 
 ### `be_close` matcher
@@ -422,7 +448,7 @@ expect(1.0 / 3.0).to be_within(0.001).of(0.333)
 ```
 
 * Conversion can be disabled by: `--keep deprecated`
-* Deprecation: Deprecated since RSpec 2.1, removed at RSpec 3.0
+* Deprecation: Deprecated since RSpec 2.1, removed in RSpec 3.0
 * See also: [New be within matcher and RSpec.deprecate fix · rspec/rspec-expectations](https://github.com/rspec/rspec-expectations/pull/32)
 
 ### `have(n).items` matcher
@@ -455,7 +481,7 @@ expect(team.players.size).to eq(3)
 expect(team.send(:players).size).to eq(3)
 ```
 
-There's an option to continue using `have(n).items` matcher with [rspec-collection_matchers](https://github.com/rspec/rspec-collection_matchers) that is an external gem extracted from `rspec-expectations`.
+There's an option to continue using `have(n).items` matcher with [rspec-collection_matchers](https://github.com/rspec/rspec-collection_matchers) that is a gem extracted from `rspec-expectations`.
 If you choose so, disable this conversion by either:
 
 * Specify `--keep have_items` option manually.
@@ -466,9 +492,35 @@ Note: `rspec-rails` 3.0 [still uses `have(n).items` matcher with `rspec-collecti
 ---
 
 * Conversion can be disabled by: `--keep have_items`
-* Deprecation: Deprecated since RSpec 2.99, removed at RSpec 3.0
+* Deprecation: Deprecated since RSpec 2.99, removed in RSpec 3.0
 * See also: [Expectations: have(x).items matchers will be moved into an external gem - The Plan for RSpec 3](http://myronmars.to/n/dev-blog/2013/07/the-plan-for-rspec-3#expectations__matchers_will_be_moved_into_an_external_gem)
 
+### One-liner expectations with `have(n).items` matcher
+
+**This conversion will be disabled automatically if `rspec-collection_matchers` or `rspec-rails` is loaded in your spec.**
+
+```ruby
+# Targets
+it { should have(3).items }
+it { should have_at_least(3).players }
+
+# Converted
+it 'has 3 items' do
+  expect(subject.size).to eq(3)
+end
+
+# With `--keep should`
+it 'has 3 items' do
+  subject.size.should == 3
+end
+
+it 'has at least 3 players' do
+  expect(subject.players.size).to be >= 3
+end
+```
+
+* Conversion can be disabled by: `--keep have_items`
+
 ### Expectations on block
 
 ```ruby
@@ -500,7 +552,7 @@ lambda { do_something }.should_not raise_error # with `--keep should`
 ```
 
 * Conversion can be disabled by: `--keep deprecated`
-* Deprecation: Deprecated since RSpec 2.14, removed at RSpec 3.0
+* Deprecation: Deprecated since RSpec 2.14, removed in RSpec 3.0
 * See also: [Consider deprecating `expect { }.not_to raise_error(SpecificErrorClass)` · rspec/rspec-expectations](https://github.com/rspec/rspec-expectations/issues/231)
 
 ### Message expectations
@@ -538,7 +590,7 @@ Klass.any_instance.stub(:foo) # with `--keep stub`
 ```
 
 * Conversion can be disabled by: `--keep deprecated`
-* Deprecation: Deprecated since RSpec 2.14, removed at RSpec 3.0
+* Deprecation: Deprecated since RSpec 2.14, removed in RSpec 3.0
 * See also: [Don't allow at_least(0) · rspec/rspec-mocks](https://github.com/rspec/rspec-mocks/issues/133)
 
 ### Method stubs
@@ -546,29 +598,38 @@ Klass.any_instance.stub(:foo) # with `--keep stub`
 ```ruby
 # Targets
 obj.stub(:foo)
-
 obj.stub!(:foo)
 
 obj.stub(:foo => 1, :bar => 2)
 
+obj.stub_chain(:foo, :bar, :baz)
+
 Klass.any_instance.stub(:foo)
 
 # Converted
 allow(obj).to receive(:foo)
 
-allow(obj).to receive(:foo)
-
-# If the target project's rspec gem dependency is prior to 3.0
+# If the target project's rspec gem dependency is prior to 3.0.0.beta1
 allow(obj).to receive(:foo).and_return(1)
 allow(obj).to receive(:bar).and_return(2)
 
-# If the target project's rspec gem dependency is 3.0 or later
+# If the target project's rspec gem dependency is 3.0.0.beta1 or later
 allow(obj).to receive_messages(:foo => 1, :bar => 2)
 
+# Conversion from `stub_chain` to `receive_message_chain` is available
+# only if the target project's rspec gem dependency is 2.99.0.beta2 or later
+allow(obj).to receive_message_chain(:foo, :bar, :baz)
+
 allow_any_instance_of(Klass).to receive(:foo)
 ```
 
-Note: `allow(obj).to receive_messages(:foo => 1, :bar => 2)` that is designed to be the replacement for `obj.stub(:foo => 1, :bar => 2)` is available from RSpec 3.0 (though [it's now being considered to be backported to RSpec 2.99](https://github.com/rspec/rspec-mocks/issues/454)). So, in [the upgrade path to RSpec 3](http://myronmars.to/n/dev-blog/2013/07/the-plan-for-rspec-3#the_upgrade_path), if you want to convert them with keeping the syntax correspondence, you need to follow these steps:
+#### No replacement for `unstub`
+
+There's no replacement for `unstub` in the `expect` syntax. See [the discussion](https://github.com/rspec/rspec-mocks/issues/153#issuecomment-12208638) for more details.
+
+#### Steps to upgrade `obj.stub(:foo => 1, :bar => 2)`
+
+`allow(obj).to receive_messages(:foo => 1, :bar => 2)` that is designed to be the replacement for `obj.stub(:foo => 1, :bar => 2)` is available from RSpec 3.0 (though [it's now being considered to be backported to RSpec 2.99](https://github.com/rspec/rspec-mocks/issues/454)). So, in [the upgrade path to RSpec 3](http://myronmars.to/n/dev-blog/2013/07/the-plan-for-rspec-3#the_upgrade_path), if you want to convert them with keeping the syntax correspondence, you need to follow these steps:
 
 1. Upgrade to RSpec 2.99
 2. Run `transpec --keep stub`
@@ -598,7 +659,7 @@ obj.unstub(:foo)
 ```
 
 * Conversion can be disabled by: `--keep deprecated`
-* Deprecation: Deprecated since RSpec 2.14, removed at RSpec 3.0
+* Deprecation: Deprecated since RSpec 2.14, removed in RSpec 3.0
 * See also: [Consider deprecating and/or removing #stub! and #unstub! at some point · rspec/rspec-mocks](https://github.com/rspec/rspec-mocks/issues/122)
 
 ### Method stubs with deprecated specification of number of times
@@ -614,7 +675,7 @@ obj.stub(:foo) # with `--keep stub`
 ```
 
 * Conversion can be disabled by: `--keep deprecated`
-* Deprecation: Deprecated since RSpec 2.14, removed at RSpec 3.0
+* Deprecation: Deprecated since RSpec 2.14, removed in RSpec 3.0
 * See also: [Don't allow at_least(0) · rspec/rspec-mocks](https://github.com/rspec/rspec-mocks/issues/133)
 
 ### Deprecated test double aliases
@@ -629,7 +690,7 @@ double('something')
 ```
 
 * Conversion can be disabled by: `--keep deprecated`
-* Deprecation: Deprecated since RSpec 2.14, removed at RSpec 3.0
+* Deprecation: Deprecated since RSpec 2.14, removed in RSpec 3.0
 * See also: [myronmarston / why_double.md - Gist](https://gist.github.com/myronmarston/6576665)
 
 ### Expectations on attribute of subject with `its`
@@ -653,7 +714,7 @@ END
 <%= Transpec::Converter.new.convert(its_target) -%>
 ```
 
-There's an option to continue using `its` with [rspec-its](https://github.com/rspec/rspec-its) that is an external gem extracted from `rspec-core`.
+There's an option to continue using `its` with [rspec-its](https://github.com/rspec/rspec-its) that is a gem extracted from `rspec-core`.
 If you choose so, disable this conversion by either:
 
 * Specify `--keep its` option manually.
@@ -662,9 +723,60 @@ If you choose so, disable this conversion by either:
 ---
 
 * Conversion can be disabled by: `--keep its`
-* Deprecation: Deprecated since RSpec 2.99, removed at RSpec 3.0
+* Deprecation: Deprecated since RSpec 2.99, removed in RSpec 3.0
 * See also: [Core: its will be moved into an external gem - The Plan for RSpec 3](http://myronmars.to/n/dev-blog/2013/07/the-plan-for-rspec-3#core__will_be_moved_into_an_external_gem)
 
+### Current example object
+
+**This conversion is available only if your project has `rspec` gem dependency `2.99.0.beta1` or later.**
+
+```ruby
+# Targets
+<%=
+example_target = <<END
+module ScreenshotHelper
+  def save_failure_screenshot
+    return unless example.exception
+    # ...
+  end
+end
+
+describe 'example page' do
+  include ScreenshotHelper
+  after { save_failure_screenshot }
+  let(:user) { User.find(example.metadata[:user_id]) }
+  # ...
+end
+END
+-%>
+
+# Converted
+<%=
+rspec_version = Transpec::RSpecVersion.new('2.99')
+Transpec::Converter.new(nil, rspec_version).convert(example_target)
+-%>
+```
+
+Here's an excerpt from [the warning for `RSpec::Core::ExampleGroup#example` and `#running_example` in RSpec 2.99](https://github.com/rspec/rspec-core/blob/7d6d2ca/lib/rspec/core/example_group.rb#L513-L527):
+
+>`RSpec::Core::ExampleGroup#example` is deprecated and will be removed in RSpec 3. There are a few options for what you can use instead:
+>
+>- `rspec-core`'s DSL methods (`it`, `before`, `after`, `let`, `subject`, etc) now yield the example as a block argument, and that is the recommended way to access the current example from those contexts.
+>- The current example is now exposed via `RSpec.current_example`, which is accessible from any context.
+>- If you can't update the code at this call site (e.g. because it is in an extension gem), you can use this snippet to continue making this method available in RSpec 2.99 and RSpec 3:
+>
+>```ruby
+>RSpec.configure do |c|
+>  c.expose_current_running_example_as :example
+>end
+>```
+
+---
+
+* Conversion can be disabled by: `--keep deprecated`
+* Deprecation: Deprecated since RSpec 2.99, removed in RSpec 3.0
+* See also: [Core: DSL methods will yield the example - The Plan for RSpec 3](http://myronmars.to/n/dev-blog/2013/07/the-plan-for-rspec-3#core_dsl_methods_will_yield_the_example)
+
 ## Compatibility
 
 Tested on MRI 1.9, MRI 2.0 and JRuby in 1.9 mode.