rspec-mocks 3.0.0.beta2 → 3.0.0.rc1

data/features/README.md

@@ -1,75 +0,0 @@
-rspec-mocks helps to control the context in a code example by letting you set
-known return values, fake implementations of methods, and even expectations
-that specific messages are received by an object.
-
-You can do these three things on test doubles that rspec-mocks creates for you
-on the fly, or you can do them on objects that are part of your system.
-
-## Messages and Methods
-
-_Message_ and _method_ are metaphors that we use somewhat interchangeably, but
-they are subtly different.  In Object Oriented Programming, objects communicate
-by sending _messages_ to one another. When an object receives a message, it
-invokes a _method_ with the same name as the message.
-
-## Test Doubles
-
-A test double is an object that stands in for another object in your system
-during a code example. Use the `double` method, passing in an optional identifier, to create one:
-
-    book = double("book")
-
-Most of the time you will want some confidence that your doubles resemble an
-existing object in your system. Verifying doubles are provided for this
-purpose. If the existing object is available, they will prevent you from adding
-stubs and expectations for methods that do not exist or that have an invalid
-number of parameters.
-
-    book = instance_double("Book", :pages => 250)
-
-Verifying doubles have some clever tricks to enable you to both test in
-isolation without your dependencies loaded while still being able to validate
-them against real objects.
-
-## Method Stubs
-
-A method stub is an instruction to an object (real or test double) to return a
-known value in response to a message:
-
-    allow(die).to receive(:roll) { 3 }
-
-This tells the `die` object to return the value `3` when it receives the `roll`
-message.
-
-## Message Expectations
-
-A message expectation is an expectation that an object should receive a
-specific message during the course of a code example:
-
-    describe Account do
-      context "when closed" do
-        it "logs an 'account closed' message" do
-          logger = double()
-          account = Account.new
-          account.logger = logger
-
-          expect(logger).to receive(:account_closed).with(account)
-
-          account.close
-        end
-      end
-    end
-
-This example specifies that the `account` object sends the `logger` the
-`account_closed` message (with itself as an argument) when it receives the
-`close` message.
-
-## Issues
-
-The documentation for rspec-mocks is a work in progress. We'll be adding
-Cucumber features over time, and clarifying existing ones.  If you have
-specific features you'd like to see added, find the existing documentation
-incomplete or confusing, or, better yet, wish to write a missing Cucumber
-feature yourself, please [submit an
-issue](http://github.com/rspec/rspec-mocks/issues) or a [pull
-request](http://github.com/rspec/rspec-mocks).

data/features/Scope.md

@@ -1,17 +0,0 @@
-Doubles, stubs, and message expectations are all cleaned out after each
-example. This ensures that each example can be run in isolation, and in any
-order.
-
-### `before(:each)`
-
-It is perfectly fine to set up doubles, stubs, and message expectations in
-a `before(:each)` hook, as that hook is executed in the scope of the example:
-
-    before(:each) do
-      @account = double('account')
-    end
-
-### Do not create doubles, stubs, or message expectations in `before(:all)`
-
-If you do, they'll get cleaned out after the first example, and you will be
-very confused as to what's going on in the second example.

data/features/Upgrade.md

@@ -1,22 +0,0 @@
-## rspec-mocks-2.6
-
-### `any_instance`
-
-Set method stubs and message expectations on any instance of a class:
-
-    class Foo; end
-    Foo.any_instance.stub(:bar) { 'bar' }
-    Foo.new.bar # => 'bar'
-
-## rspec-mocks-2.2
-
-### `require "rspec/mocks/standalone"`
-
-Sets up top-level environment to explore rspec-mocks. Mostly useful in irb:
-
-    $ irb
-    > require 'rspec/mocks/standalone'
-    > foo = double()
-    > foo.stub(:bar) { :baz }
-    > foo.bar
-      => :baz

data/features/argument_matchers/README.md

@@ -1,27 +0,0 @@
-### Introduction
-
-Argument matchers can be used:
-
-* In stubs to constrain the scope of the stubbed method
-
-    allow(obj).to receive(:foo).with(:bar) do |arg|
-      #do something for :bar
-    end
-    allow(obj).to receive(:foo).with(:baz) do |arg|
-      #do something for :baz
-    end
-
-* In expectations to validate the arguments that should be received in a method call
-
-    #create a double
-    obj = double()
-
-    #expect a message with given args
-    expect(obj).to receive(:message).with('an argument')
-
-If more control is needed, one can use a block
-
-    expect(obj).to receive(:message) do |arg1,  arg2|
-      # set expectations about the args in this block
-      # and optionally set a return value
-    end

data/features/argument_matchers/explicit.feature

@@ -1,59 +0,0 @@
-Feature: explicit arguments
-
-  Allows you to explicitly specify the argument values
-
-  Scenario: explicit arguments
-    Given a file named "stub_explicit_args_spec.rb" with:
-      """ruby
-      describe "stubbed explicit arguments" do
-        it "works on stubs" do
-          object = Object.new
-          allow(object).to receive(:foo).with(:this) do |arg|
-            "got this"
-          end
-          allow(object).to receive(:foo).with(:that) do |arg|
-            "got that"
-          end
-
-          expect(object.foo(:this)).to eq("got this")
-          expect(object.foo(:that)).to eq("got that")
-        end
-
-        it "works on doubles and expectations" do
-          object = double('foo')
-          expect(object).to receive(:bar).with(:foo)
-
-          object.bar(:foo)
-        end
-      end
-      """
-    When I run `rspec stub_explicit_args_spec.rb`
-    Then the output should contain "2 examples, 0 failures"
-
-  Scenario: explicit arguments with multiple arities
-    Given a file named "stub_multiple_explicit_args_spec.rb" with:
-      """ruby
-      describe "stubbed multiple explicit arguments" do
-        it "works on stubs" do
-          object = Object.new
-          allow(object).to receive(:foo).with(:this) do |arg|
-            "got this"
-          end
-          allow(object).to receive(:foo).with(:this, :that) do |arg1, arg2|
-            "got this and that"
-          end
-
-          expect(object.foo(:this)).to eq("got this")
-          expect(object.foo(:this, :that)).to eq("got this and that")
-        end
-
-        it "works on mocks" do
-          object = double('foo')
-          expect(object).to receive(:foo).with(:this, :that)
-
-          object.foo(:this, :that)
-        end
-      end
-      """
-    When I run `rspec stub_multiple_explicit_args_spec.rb`
-    Then the output should contain "2 examples, 0 failures"

data/features/argument_matchers/general_matchers.feature

@@ -1,85 +0,0 @@
-Feature: General matchers
-
-  The `anything`,  `any_args`,  and `no_args` matchers can be used to require the method
-  to have arguments (or not) without constraining the details of the argument, such as its
-  type,  pattern or value. The `anything` matcher only reflects a single argument, while
-  the `any_args` matcher matches any arity.
-
-  Scenario: anything argument matcher
-    Given a file named "stub_anything_args_spec.rb" with:
-      """ruby
-      describe "stubbed anything() args spec" do
-        it "works" do
-          object = Object.new
-          allow(object).to receive(:foo).with(anything) do
-            "anything"
-          end
-
-          expect(object.foo(1)).to eq("anything")
-          expect(object.foo(:that)).to eq("anything")
-        end
-      end
-      """
-    When I run `rspec stub_anything_args_spec.rb`
-    Then the output should contain "1 example, 0 failures"
-
-  Scenario: any_args argument matcher
-    Given a file named "stub_any_args_spec.rb" with:
-      """ruby
-      describe "stubbed any_args() args spec" do
-        it "works" do
-          object = Object.new
-          allow(object).to receive(:foo).with(any_args) do
-            "anything"
-          end
-
-          expect(object.foo(1)).to eq("anything")
-          expect(object.foo(:that)).to eq("anything")
-          expect(object.foo).to eq("anything")
-        end
-      end
-      """
-    When I run `rspec stub_any_args_spec.rb`
-    Then the output should contain "1 example, 0 failures"
-
-  Scenario: no_args argument matcher
-    Given a file named "stub_no_args_spec.rb" with:
-      """ruby
-      describe "stubbed no_args() args spec" do
-        it "works for no args" do
-          object = Object.new
-          allow(object).to receive(:foo).with(no_args) do
-            "nothing"
-          end
-          allow(object).to receive(:foo).with(anything) do
-            "something"
-          end
-
-          expect(object.foo(:that)).to eq("something")
-          expect(object.foo).to eq("nothing")
-        end
-      end
-      """
-    When I run `rspec stub_no_args_spec.rb`
-    Then the output should contain "1 example, 0 failures"
-
-  Scenario: no_args argument matcher for expectations
-    Given a file named "stub_no_args_expectations_spec.rb" with:
-      """ruby
-      describe "stubbed no_args() args spec for expectations" do
-        it "works for no args" do
-          object = Object.new
-          expect(object).to receive(:foo).with(no_args)
-
-          object.foo
-        end
-        it "fails for args" do
-          object = Object.new
-          expect(object).to receive(:foo).with(no_args)
-
-          object.foo(:bar)
-        end
-      end
-      """
-    When I run `rspec stub_no_args_expectations_spec.rb`
-    Then the output should contain "2 examples, 1 failure"

data/features/argument_matchers/type_matchers.feature

@@ -1,26 +0,0 @@
-Feature: stub with argument constraints
-
-  You can further specify the behavior by constraining the type,
-  format and/or number of arguments with the `#with()` method
-  chained off of `#stub()`
-
-  Scenario: an_instance_of argument matcher
-    Given a file named "stub_an_instance_of_args_spec.rb" with:
-      """ruby
-      describe "stubbed an_instance_of() args spec" do
-        it "works" do
-          object = Object.new
-          allow(object).to receive(:foo).with(an_instance_of(Symbol)) do
-            "symbol"
-          end
-          allow(object).to receive(:foo).with(an_instance_of(String)) do
-            "string"
-          end
-
-          expect(object.foo("bar")).to eq("string")
-          expect(object.foo(:that)).to eq("symbol")
-        end
-      end
-      """
-    When I run `rspec stub_an_instance_of_args_spec.rb`
-    Then the output should contain "1 example, 0 failures"

data/features/message_expectations/README.md

@@ -1,75 +0,0 @@
-### Basics
-
-    # create a double
-    obj = double()
-
-    # expect a message
-    expect(obj).to receive(:message)
-
-    # specify a return value
-    expect(obj).to receive(:message) { :value }
-    expect(obj).to receive(:message).and_return(:value)
-
-    # specify multiple message/return value pairs
-    expect(obj).to receive_messages(:message => :value, :another_message => :another_value)
-
-These forms are somewhat interchangeable. The difference is that the
-block contents are evaluated lazily when the `obj` receives the
-`message` message, whereas the others are evaluated as they are read.
-
-### Fake implementation
-
-    expect(obj).to receive(:message) do |arg1, arg2|
-      # set expectations about the args in this block
-      # and set a return value
-    end
-
-### Using the original implementation
-
-    expect(obj).to receive(:message).and_call_original
-
-### Raising/Throwing
-
-    expect(obj).to receive(:message).and_raise("this error")
-    expect(obj).to receive(:message).and_throw(:this_symbol)
-
-You can also use the block format:
-
-    expect(obj).to receive(:message) { raise "this error" }
-    expect(obj).to receive(:message) { throw :this_symbol }
-
-### Argument constraints
-
-#### Explicit arguments
-
-    expect(obj).to receive(:message).with('an argument')
-    expect(obj).to receive(:message).with('more_than', 'one_argument')
-
-#### Argument matchers
-
-    expect(obj).to receive(:message).with(anything())
-    expect(obj).to receive(:message).with(an_instance_of(Money))
-    expect(obj).to receive(:message).with(hash_including(:a => 'b'))
-
-#### Regular expressions
-
-    expect(obj).to receive(:message).with(/abc/)
-
-### Counts
-
-    expect(obj).to receive(:message).once
-    expect(obj).to receive(:message).twice
-    expect(obj).to receive(:message).exactly(3).times
-
-    expect(obj).to receive(:message).at_least(:once)
-    expect(obj).to receive(:message).at_least(:twice)
-    expect(obj).to receive(:message).at_least(n).times
-
-    expect(obj).to receive(:message).at_most(:once)
-    expect(obj).to receive(:message).at_most(:twice)
-    expect(obj).to receive(:message).at_most(n).times
-
-### Ordering
-
-    expect(obj).to receive(:one).ordered
-    expect(obj).to receive(:two).ordered

data/features/message_expectations/allow_any_instance_of.feature

@@ -1,26 +0,0 @@
-Feature: allow a message on any instance of a class
-
-  Use `allow_any_instance_of(Class).to receive` when you want to configure how
-  instances of the given class respond to a message without setting an
-  expectation that the message will be received.
-
-  Scenario: allowing a message on any instance of a class
-    Given a file named "example_spec.rb" with:
-      """ruby
-      describe "any_instance.to receive" do
-        before do
-          allow_any_instance_of(Object).to receive(:foo).and_return(:return_value)
-        end
-
-        it "allows any instance of the class to receive the message" do
-          o = Object.new
-          expect(o.foo).to eq(:return_value)
-        end
-
-        it "passes even if no instances receive that message" do
-          o = Object.new
-        end
-      end
-      """
-    When I run `rspec example_spec.rb`
-    Then the examples should all pass

data/features/message_expectations/any_instance.feature

@@ -1,43 +0,0 @@
-Feature: expect a message on any instance of a class
-
-  Use `expect_any_instance_of(Class).to receive` to set an expectation that one
-  (and only one) instance of a class receives a message before the example is
-  completed.
-
-  The example will fail if no instance receives the specified message.
-
-  Scenario: expect a message on any instance of a class
-    Given a file named "example_spec.rb" with:
-    """ruby
-      describe "expect_any_instance_of" do
-        before do
-          expect_any_instance_of(Object).to receive(:foo).and_return(:return_value)
-        end
-
-        it "verifies that one instance of the class receives the message" do
-          o = Object.new
-          expect(o.foo).to eq(:return_value)
-        end
-
-        it "fails unless an instance receives that message" do
-        end
-      end
-      """
-    When I run `rspec example_spec.rb`
-    Then the output should contain "2 examples, 1 failure"
-    And the output should contain "1) expect_any_instance_of fails unless an instance receives that message"
-
-  Scenario: expect a message on any instance of a class (should syntax)
-    Given a file named "example_spec.rb" with:
-      """ruby
-      describe "any_instance.should_receive" do
-        it "verifies that one instance of the class receives the message" do
-          Object.any_instance.should_receive(:foo).and_return(:return_value)
-
-          o = Object.new
-          expect(o.foo).to eq(:return_value)
-        end
-      end
-      """
-    When I run `rspec example_spec.rb`
-    Then the examples should all pass