transpec 1.6.1 → 1.7.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 5c6f45e13cea25a0a7b868b61b75167e862c7fb2
-  data.tar.gz: d34f0aab8e600dd52627e25d1e636c6c130ef419
+  metadata.gz: c46495e8ece5679b985320ebfd8f026bd089fa0f
+  data.tar.gz: 3096577bb24dfc010639d541e8f3471a5568cba1
 SHA512:
-  metadata.gz: bf29aecabd3c9ee734eaae5f751d60fb032cc1dd4ccd2909ac27cbe76fe1e61e0dcae77e27794232bc9c99ce4c501490684aded1f6ee8c920624116deda96998
-  data.tar.gz: ae26aaec177b656156b01db64afb3a5c644b08448795f3d82ccd51d17bedacb62bf6cb13d80de2992b5286bfd7e24ae69da4909cc31e059022db5a8a576ff6e9
+  metadata.gz: 81b9a2e1fe74cb4125f8ea25790198f528200973073a253c3d8facb5e036f883cc5dd9d7b519ac59705580f395a79baaac854f2055f96c31032087bd233b0237
+  data.tar.gz: 7c34385af11c5d9eee744d334141820f47436c907d26e8d1f66a7bb8391e3835698f24bdddc2a60e22635933c242fa3dbeb0b6855170b8324a6ed6735ec7f4d5

data/.rubocop.yml

@@ -48,10 +48,6 @@ AlignHash:
 Documentation:
   Enabled: false
 
-# Currently IndentationWidth reports false positive offence around here document.
-IndentationWidth:
-  Enabled: false
-
 # TODO: This should not register offences for non keyword hashes.
 BracesAroundHashParameters:
   Enabled: false

data/.travis.yml

@@ -2,6 +2,7 @@ language: ruby
 rvm:
   - 1.9.3
   - 2.0.0
-  - 2.1.0-rc1
+  - 2.1.0
   - jruby-19mode
+before_install: gem update --remote bundler
 script: bundle exec rake travis

data/CHANGELOG.md

@@ -2,6 +2,10 @@
 
 ## Development
 
+## v1.7.0
+
+* Support conversion of `any_instance` block
+
 ## v1.6.1
 
 * Handle deprecation messages from `rainbow` gem

data/Guardfile

@@ -4,7 +4,7 @@
 # This group allows to skip running RuboCop if RSpec failed,
 # like Red > Green (RSpec) > Refactor (RuboCop).
 group :red_green_refactor, halt_on_fail: true do
-  guard :rspec, all_after_pass: true, all_on_start: true, cmd: 'bundle exec rspec' do
+  guard :rspec, all_on_start: true, failed_mode: :keep, cmd: 'bundle exec rspec' do
     watch(%r{^spec/.+_spec\.rb$})
     watch(%r{^lib/(.+)\.rb$})        { |m| "spec/#{m[1]}_spec.rb" }
     watch('spec/spec_helper.rb')     { "spec" }

data/README.md

@@ -145,7 +145,7 @@ After the conversion, run `rspec` again and check whether everything is green:
 $ bundle exec rspec
 ```
 
-If it's green, commit the changes with an auto-generated message that describes the conversion summary:
+If it's green, commit the changes with an auto-generated message which describes the conversion summary:
 
 ```bash
 $ git commit -aeF .git/COMMIT_EDITMSG
@@ -153,6 +153,27 @@ $ git commit -aeF .git/COMMIT_EDITMSG
 
 And you are done!
 
+## Advanced Usage
+
+You can pass `transpec` arbitrary paths to be converted:
+
+```bash
+# You always need to be in the project root directory
+$ cd some-project
+
+# Convert only files in `features` directory
+$ transpec features
+
+# Convert only files in `spec/foo` and `spec/bar` directory
+$ transpec spec/foo spec/bar
+
+# Convert only `spec/baz_spec.rb`
+$ transpec spec/baz_spec.rb
+```
+
+Note that the current working directory always needs to be the project root directory,
+so that Transpec can copy the project in dynamic analysis.
+
 ## Upgrade Process to RSpec 3 beta
 
 If you are going to use Transpec in the upgrade process to RSpec 3 beta, read the article by [Myron Marston](https://github.com/myronmarston):
@@ -181,7 +202,7 @@ Skip dynamic analysis and convert with only static analysis. Note that specifyin
 
 ### `-c/--rspec-command`
 
-Specify a command to run your specs that is used for dynamic analysis.
+Specify a command to run your specs which is used 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.
@@ -201,21 +222,24 @@ $ transpec --keep should_receive,stub
 
 #### Available syntax types
 
-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(n).items`   | `expect(obj.size).to eq(n)`
-`its`            | `its(:attr) { }`                 | `describe { subject { }; it { } }`
-`deprecated`     | `obj.stub!`, `mock('foo')`, etc. | `obj.stub`, `double('foo')`
+Note that some syntaxes are available only if your project's RSpec is specific version or later.
+If they are unavailable, conversions for such syntaxes will be disabled automatically.
+
+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(:message)` | `expect(obj).to receive(:message)`
+`stub`           | `obj.stub(:message)`           | `allow(obj).to receive(:message)`
+`have_items`     | `expect(obj).to have(n).items` | `expect(obj.size).to eq(n)`
+`its`            | `its(:attr) { }`               | `describe '#attr' { subject { }; it { } }`
+`deprecated`     | All other deprecated syntaxes  | Latest syntaxes
 
 See [Supported Conversions](#supported-conversions) for more details.
 
 ### `-n/--negative-form`
 
-Specify a negative form of `to` that is used in the `expect` syntax.
+Specify a negative form of `to` which is used in the `expect` syntax.
 Either `not_to` or `to_not`.
 `not_to` is used by default.
 
@@ -225,7 +249,7 @@ $ transpec --negative-form to_not
 
 ### `-b/--boolean-matcher`
 
-Specify a matcher type that `be_true` and `be_false` will be converted to.
+Specify a boolean matcher type which `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.
 
@@ -235,6 +259,17 @@ $ transpec --boolean-matcher true,false
 
 See [Supported Conversions - Boolean matchers](#boolean-matchers) for more details.
 
+### `-a/--no-yield-any-instance`
+
+Suppress yielding receiver instances to `any_instance` implementation blocks as the first block argument.
+
+By default in RSpec 3, `any_instance` implementation blocks will be yielded the receiving
+instance as the first block argument, and by default Transpec converts specs by adding instance arguments to the blocks so that they conform to the behavior of RSpec 3.
+Specifying this option suppresses the conversion and keeps them compatible with RSpec 2.
+Note that this is not same as `--keep deprecated` since this configures `yield_receiver_to_any_instance_implementation_blocks` with `RSpec.configure`.
+
+See [Supported Conversions - `any_instance` implementation blocks](#any_instance-implementation-blocks) for more details.
+
 ### `-p/--no-parentheses-matcher-arg`
 
 Suppress parenthesizing arguments of matchers when converting
@@ -306,7 +341,7 @@ end
 ### Reason
 
 * `should` is defined on `BasicObject` class, so you can use `should` everywhere.
-* `expect` is defined on `RSpec::Matchers` module that is included by `RSpec::Core::ExampleGroup` class, so you can use `expect` only where `self` is an instance of `RSpec::Core::ExampleGroup` (i.e. in `it` blocks, `:each` hook blocks or included module methods) or other classes that explicitly include `RSpec::Matchers`.
+* `expect` is defined on `RSpec::Matchers` module which is included by `RSpec::Core::ExampleGroup` class, so you can use `expect` only where `self` is an instance of `RSpec::Core::ExampleGroup` (i.e. in `it` blocks, `:each` hook blocks or included module methods) or other classes that explicitly include `RSpec::Matchers`.
 
 With the above example, in the context of `1.should == 1`, the `self` is an instance of `MyAwesomeTestRunner`.
 Transpec tracks contexts and skips conversion if the target syntax cannot be converted in a case like this.
@@ -327,6 +362,43 @@ Include or extend `RSpec::Matchers` module to make `expect` available in the con
 
 Then run `transpec` again.
 
+## Two Types of `should`
+
+There are two types of `should`:
+
+```ruby
+describe 'the monkey-patched should' do
+  subject { [] }
+
+  it 'is empty' do
+    subject.should be_empty
+    #       ^^^^^^ BasicObject#should in RSpec 2.11 or later,
+    #                or Kernel#should prior to RSpec 2.11.
+  end
+end
+
+describe 'the one-liner should' do
+  subject { [] }
+
+  it { should be_empty }
+  #    ^^^^^^ RSpec::Core::ExampleGroup#should
+end
+```
+
+The monkey-patched `obj.should`:
+
+* Is provided by `rspec-expectations` gem.
+* Is deprecated in RSpec 3.
+* Has [the issue](http://myronmars.to/n/dev-blog/2012/06/rspecs-new-expectation-syntax#delegation_issues) with delegate/proxy objects.
+* There's the alternative syntax [`expect(obj).to`](#standard-expectations) since RSpec 2.11.
+
+The one-liner (implicit receiver) `should`:
+
+* Is provided by `rspec-core` gem.
+* Is _not_ deprecated in RSpec 3.
+* Does _not_ have the issue with delegate/proxy objects.
+* There's the alternative syntax [`is_expected.to`](#one-liner-expectations) since RSpec 2.99.beta2 (not yet released).
+
 ## Supported Conversions
 
 ### Standard expectations
@@ -509,7 +581,7 @@ Note: `rspec-rails` 3.0 [still uses `have(n).items` matcher with `rspec-collecti
 
 * This conversion can be disabled by: `--keep have_items`
 * 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)
+* 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
 
@@ -669,7 +741,7 @@ There's no replacement for `unstub` in the `expect` syntax. See [this discussion
 
 #### 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:
+`allow(obj).to receive_messages(:foo => 1, :bar => 2)` which 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`
@@ -727,6 +799,84 @@ obj.stub(:foo) # with `--keep stub`
 * 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)
 
+### `any_instance` implementation blocks
+
+**This conversion is available only if your project's RSpec is `>= 2.99.0.beta1` and `< 3.0.0.beta1`.**
+
+Targets:
+
+```ruby
+RSpec.configure do |rspec|
+end
+
+describe 'example' do
+  it 'is any_instance implementation block' do
+    Klass.any_instance.should_receive(:message) { |arg| puts arg }
+    Klass.any_instance.stub(:message) { |arg| puts arg }
+    expect_any_instance_of(Klass).to receive(:message) { |arg| puts arg }
+    allow_any_instance_of(Klass).to receive(:message) { |arg| puts arg }
+  end
+end
+```
+
+Will be converted to:
+
+```ruby
+RSpec.configure do |rspec|
+  rspec.mock_with :rspec do |mocks|
+    mocks.yield_receiver_to_any_instance_implementation_blocks = true
+  end
+end
+
+describe 'example' do
+  it 'is any_instance implementation block' do
+    expect_any_instance_of(Klass).to receive(:message) { |instance, arg| puts arg }
+    allow_any_instance_of(Klass).to receive(:message) { |instance, arg| puts arg }
+    expect_any_instance_of(Klass).to receive(:message) { |instance, arg| puts arg }
+    allow_any_instance_of(Klass).to receive(:message) { |instance, arg| puts arg }
+  end
+end
+
+# With `--no-yield-any-instance`
+RSpec.configure do |rspec|
+  rspec.mock_with :rspec do |mocks|
+    mocks.yield_receiver_to_any_instance_implementation_blocks = false
+  end
+end
+
+describe 'example' do
+  it 'is any_instance implementation block' do
+    expect_any_instance_of(Klass).to receive(:message) { |arg| puts arg }
+    allow_any_instance_of(Klass).to receive(:message) { |arg| puts arg }
+    expect_any_instance_of(Klass).to receive(:message) { |arg| puts arg }
+    allow_any_instance_of(Klass).to receive(:message) { |arg| puts arg }
+  end
+end
+```
+
+Here's an excerpt from [the warning](https://github.com/rspec/rspec-mocks/blob/aab8dc9/lib/rspec/mocks/message_expectation.rb#L478-L491) for `any_instance` implementation blocks in RSpec 2.99:
+
+> In RSpec 3, `any_instance` implementation blocks will be yielded the receiving
+> instance as the first block argument to allow the implementation block to use
+> the state of the receiver.  To maintain compatibility with RSpec 3 you need to
+> either set rspec-mocks' `yield_receiver_to_any_instance_implementation_blocks`
+> config option to `false` OR set it to `true` and update your `any_instance`
+> implementation blocks to account for the first block argument being the receiving instance.
+>
+> To set the config option, use a snippet like:
+>
+> ```ruby
+> RSpec.configure do |rspec|
+>   rspec.mock_with :rspec do |mocks|
+>     mocks.yield_receiver_to_any_instance_implementation_blocks = false
+>   end
+> end
+> ```
+
+* This conversion can be disabled by: `--keep deprecated`
+* Deprecation: deprecated since RSpec 2.99
+* See also: [Mocks: `any_instance` block implementations will yield the receiver](http://myronmars.to/n/dev-blog/2013/07/the-plan-for-rspec-3#mocks__block_implementations_will_yield_the_receiver)
+
 ### Deprecated test double aliases
 
 Targets:
@@ -797,7 +947,7 @@ If you choose to do so, disable this conversion by either:
 
 * This conversion can be disabled by: `--keep its`
 * 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)
+* 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
 
@@ -839,7 +989,7 @@ describe 'example page' do
 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):
+Here's an excerpt from [the warning](https://github.com/rspec/rspec-core/blob/7d6d2ca/lib/rspec/core/example_group.rb#L513-L527) for `RSpec::Core::ExampleGroup#example` and `#running_example` in RSpec 2.99:
 
 > `RSpec::Core::ExampleGroup#example` is deprecated and will be removed in RSpec 3. There are a few options for what you can use instead:
 >

data/README.md.erb

@@ -118,7 +118,7 @@ After the conversion, run `rspec` again and check whether everything is green:
 $ bundle exec rspec
 ```
 
-If it's green, commit the changes with an auto-generated message that describes the conversion summary:
+If it's green, commit the changes with an auto-generated message which describes the conversion summary:
 
 ```bash
 $ git commit -aeF .git/COMMIT_EDITMSG
@@ -126,6 +126,27 @@ $ git commit -aeF .git/COMMIT_EDITMSG
 
 And you are done!
 
+## Advanced Usage
+
+You can pass `transpec` arbitrary paths to be converted:
+
+```bash
+# You always need to be in the project root directory
+$ cd some-project
+
+# Convert only files in `features` directory
+$ transpec features
+
+# Convert only files in `spec/foo` and `spec/bar` directory
+$ transpec spec/foo spec/bar
+
+# Convert only `spec/baz_spec.rb`
+$ transpec spec/baz_spec.rb
+```
+
+Note that the current working directory always needs to be the project root directory,
+so that Transpec can copy the project in dynamic analysis.
+
 ## Upgrade Process to RSpec 3 beta
 
 If you are going to use Transpec in the upgrade process to RSpec 3 beta, read the article by [Myron Marston](https://github.com/myronmarston):
@@ -154,7 +175,7 @@ Skip dynamic analysis and convert with only static analysis. Note that specifyin
 
 ### `-c/--rspec-command`
 
-Specify a command to run your specs that is used for dynamic analysis.
+Specify a command to run your specs which is used 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.
@@ -174,17 +195,20 @@ $ transpec --keep should_receive,stub
 
 #### Available syntax types
 
-Type             | Target Syntax                    | Converted Syntax
------------------|----------------------------------|-----------------------------------
+Note that some syntaxes are available only if your project's RSpec is specific version or later.
+If they are unavailable, conversions for such syntaxes will be disabled automatically.
+
+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(n).items`   | `expect(obj.size).to eq(n)`
-`its`            | `its(:attr) { }`                 | `describe { subject { }; it { } }`
-`deprecated`     | `obj.stub!`, `mock('foo')`, etc. | `obj.stub`, `double('foo')`
+`should`         | `obj.should matcher`           | `expect(obj).to matcher`
+`oneliner`       | `it { should ... }`            | `it { is_expected.to ... }`
+`should_receive` | `obj.should_receive(:message)` | `expect(obj).to receive(:message)`
+`stub`           | `obj.stub(:message)`           | `allow(obj).to receive(:message)`
+`have_items`     | `expect(obj).to have(n).items` | `expect(obj.size).to eq(n)`
+`its`            | `its(:attr) { }`               | `describe '#attr' { subject { }; it { } }`
+`deprecated`     | All other deprecated syntaxes  | Latest syntaxes
 END
 
 types_in_readme = conversion_type_table.lines.map do |line|
@@ -206,7 +230,7 @@ See [Supported Conversions](#supported-conversions) for more details.
 
 ### `-n/--negative-form`
 
-Specify a negative form of `to` that is used in the `expect` syntax.
+Specify a negative form of `to` which is used in the `expect` syntax.
 Either `not_to` or `to_not`.
 `not_to` is used by default.
 
@@ -216,7 +240,7 @@ $ transpec --negative-form to_not
 
 ### `-b/--boolean-matcher`
 
-Specify a matcher type that `be_true` and `be_false` will be converted to.
+Specify a boolean matcher type which `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.
 
@@ -226,6 +250,17 @@ $ transpec --boolean-matcher true,false
 
 See [Supported Conversions - Boolean matchers](#boolean-matchers) for more details.
 
+### `-a/--no-yield-any-instance`
+
+Suppress yielding receiver instances to `any_instance` implementation blocks as the first block argument.
+
+By default in RSpec 3, `any_instance` implementation blocks will be yielded the receiving
+instance as the first block argument, and by default Transpec converts specs by adding instance arguments to the blocks so that they conform to the behavior of RSpec 3.
+Specifying this option suppresses the conversion and keeps them compatible with RSpec 2.
+Note that this is not same as `--keep deprecated` since this configures `yield_receiver_to_any_instance_implementation_blocks` with `RSpec.configure`.
+
+See [Supported Conversions - `any_instance` implementation blocks](#any_instance-implementation-blocks) for more details.
+
 ### `-p/--no-parentheses-matcher-arg`
 
 Suppress parenthesizing arguments of matchers when converting
@@ -302,7 +337,7 @@ end
 ### Reason
 
 * `should` is defined on `BasicObject` class, so you can use `should` everywhere.
-* `expect` is defined on `RSpec::Matchers` module that is included by `RSpec::Core::ExampleGroup` class, so you can use `expect` only where `self` is an instance of `RSpec::Core::ExampleGroup` (i.e. in `it` blocks, `:each` hook blocks or included module methods) or other classes that explicitly include `RSpec::Matchers`.
+* `expect` is defined on `RSpec::Matchers` module which is included by `RSpec::Core::ExampleGroup` class, so you can use `expect` only where `self` is an instance of `RSpec::Core::ExampleGroup` (i.e. in `it` blocks, `:each` hook blocks or included module methods) or other classes that explicitly include `RSpec::Matchers`.
 
 With the above example, in the context of `1.should == 1`, the `self` is an instance of `MyAwesomeTestRunner`.
 Transpec tracks contexts and skips conversion if the target syntax cannot be converted in a case like this.
@@ -323,6 +358,43 @@ Include or extend `RSpec::Matchers` module to make `expect` available in the con
 
 Then run `transpec` again.
 
+## Two Types of `should`
+
+There are two types of `should`:
+
+```ruby
+describe 'the monkey-patched should' do
+  subject { [] }
+
+  it 'is empty' do
+    subject.should be_empty
+    #       ^^^^^^ BasicObject#should in RSpec 2.11 or later,
+    #                or Kernel#should prior to RSpec 2.11.
+  end
+end
+
+describe 'the one-liner should' do
+  subject { [] }
+
+  it { should be_empty }
+  #    ^^^^^^ RSpec::Core::ExampleGroup#should
+end
+```
+
+The monkey-patched `obj.should`:
+
+* Is provided by `rspec-expectations` gem.
+* Is deprecated in RSpec 3.
+* Has [the issue](http://myronmars.to/n/dev-blog/2012/06/rspecs-new-expectation-syntax#delegation_issues) with delegate/proxy objects.
+* There's the alternative syntax [`expect(obj).to`](#standard-expectations) since RSpec 2.11.
+
+The one-liner (implicit receiver) `should`:
+
+* Is provided by `rspec-core` gem.
+* Is _not_ deprecated in RSpec 3.
+* Does _not_ have the issue with delegate/proxy objects.
+* There's the alternative syntax [`is_expected.to`](#one-liner-expectations) since RSpec 2.99.beta2 (not yet released).
+
 ## Supported Conversions
 
 ### Standard expectations
@@ -505,7 +577,7 @@ Note: `rspec-rails` 3.0 [still uses `have(n).items` matcher with `rspec-collecti
 
 * This conversion can be disabled by: `--keep have_items`
 * 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)
+* 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
 
@@ -665,7 +737,7 @@ There's no replacement for `unstub` in the `expect` syntax. See [this discussion
 
 #### 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:
+`allow(obj).to receive_messages(:foo => 1, :bar => 2)` which 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`
@@ -723,6 +795,70 @@ obj.stub(:foo) # with `--keep stub`
 * 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)
 
+### `any_instance` implementation blocks
+
+**This conversion is available only if your project's RSpec is `>= <%= Transpec::RSpecVersion::ANY_INSTANCE_IMPLEMENTATION_BLOCK_MIGRATION_BEGIN %>` and `< <%= Transpec::RSpecVersion::ANY_INSTANCE_IMPLEMENTATION_BLOCK_MIGRATION_EXCLUSIVE_END %>`.**
+
+Targets:
+
+```ruby
+<%=
+any_instance_block_target = <<END
+RSpec.configure do |rspec|
+end
+
+describe 'example' do
+  it 'is any_instance implementation block' do
+    Klass.any_instance.should_receive(:message) { |arg| puts arg }
+    Klass.any_instance.stub(:message) { |arg| puts arg }
+    expect_any_instance_of(Klass).to receive(:message) { |arg| puts arg }
+    allow_any_instance_of(Klass).to receive(:message) { |arg| puts arg }
+  end
+end
+END
+-%>
+```
+
+Will be converted to:
+
+```ruby
+<%=
+rspec_version = Transpec::RSpecVersion.yielding_receiver_to_any_instance_implementation_block_available_version
+Transpec::Converter.new(nil, rspec_version).convert(any_instance_block_target)
+-%>
+
+# With `--no-yield-any-instance`
+<%=
+configuration = Transpec::Configuration.new
+configuration.add_receiver_arg_to_any_instance_implementation_block = false
+rspec_version = Transpec::RSpecVersion.yielding_receiver_to_any_instance_implementation_block_available_version
+Transpec::Converter.new(configuration, rspec_version).convert(any_instance_block_target)
+-%>
+```
+
+Here's an excerpt from [the warning](https://github.com/rspec/rspec-mocks/blob/aab8dc9/lib/rspec/mocks/message_expectation.rb#L478-L491) for `any_instance` implementation blocks in RSpec 2.99:
+
+> In RSpec 3, `any_instance` implementation blocks will be yielded the receiving
+> instance as the first block argument to allow the implementation block to use
+> the state of the receiver.  To maintain compatibility with RSpec 3 you need to
+> either set rspec-mocks' `yield_receiver_to_any_instance_implementation_blocks`
+> config option to `false` OR set it to `true` and update your `any_instance`
+> implementation blocks to account for the first block argument being the receiving instance.
+>
+> To set the config option, use a snippet like:
+>
+> ```ruby
+> RSpec.configure do |rspec|
+>   rspec.mock_with :rspec do |mocks|
+>     mocks.yield_receiver_to_any_instance_implementation_blocks = false
+>   end
+> end
+> ```
+
+* This conversion can be disabled by: `--keep deprecated`
+* Deprecation: deprecated since RSpec 2.99
+* See also: [Mocks: `any_instance` block implementations will yield the receiver](http://myronmars.to/n/dev-blog/2013/07/the-plan-for-rspec-3#mocks__block_implementations_will_yield_the_receiver)
+
 ### Deprecated test double aliases
 
 Targets:
@@ -777,7 +913,7 @@ If you choose to do so, disable this conversion by either:
 
 * This conversion can be disabled by: `--keep its`
 * 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)
+* 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
 
@@ -814,7 +950,7 @@ 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):
+Here's an excerpt from [the warning](https://github.com/rspec/rspec-core/blob/7d6d2ca/lib/rspec/core/example_group.rb#L513-L527) for `RSpec::Core::ExampleGroup#example` and `#running_example` in RSpec 2.99:
 
 > `RSpec::Core::ExampleGroup#example` is deprecated and will be removed in RSpec 3. There are a few options for what you can use instead:
 >