gem_repackager 0.1.0

data/support/gems/rspec-mocks-2.11.1/features/method_stubs/as_null_object.feature

@@ -0,0 +1,35 @@
+Feature: as_null_object
+
+  Use the `as_null_object` method to ignore any messages that aren't explicitly
+  set as stubs or message expectations.
+
+  EXCEPTION: `to_ary` will raise a NoMethodError unless explicitly stubbed in
+  order to support `flatten` on an Array containing a double.
+
+  Scenario: double acting as_null_object 
+    Given a file named "as_null_object_spec.rb" with:
+      """
+      describe "a double with as_null_object called" do
+        let(:null_object) { double('null object').as_null_object }
+
+        it "responds to any method that is not defined" do
+          null_object.should respond_to(:an_undefined_method)
+        end
+
+        it "allows explicit stubs" do
+          null_object.stub(:foo) { "bar" }
+          null_object.foo.should eq("bar")
+        end
+
+        it "allows explicit expectations" do
+          null_object.should_receive(:something)
+          null_object.something
+        end
+
+        it "supports Array#flatten" do
+          [null_object].flatten.should eq([null_object])
+        end
+      end
+      """
+    When I run `rspec as_null_object_spec.rb`
+    Then the examples should all pass

data/support/gems/rspec-mocks-2.11.1/features/method_stubs/simple_return_value.feature

@@ -0,0 +1,64 @@
+Feature: stub with a simple return value
+
+  Use the `stub` method on a test double or a real object to tell the object to
+  return a value (or values) in response to a given message. Nothing happens if
+  the message is never received.
+
+  Scenario: stub with no return value
+    Given a file named "example_spec.rb" with:
+      """
+      describe "a stub with no return value specified" do
+        let(:collaborator) { double("collaborator") }
+
+        it "returns nil" do
+          collaborator.stub(:message)
+          collaborator.message.should be(nil)
+        end
+      end
+      """
+    When I run `rspec example_spec.rb`
+    Then the examples should all pass
+
+  Scenario: stubs with return values
+    Given a file named "example_spec.rb" with:
+      """
+      describe "a stub with a return value" do
+        context "specified in a block" do
+          it "returns the specified value" do
+            collaborator = double("collaborator")
+            collaborator.stub(:message) { :value }
+            collaborator.message.should eq(:value)
+          end
+        end
+
+        context "specified with #and_return" do
+          it "returns the specified value" do
+            collaborator = double("collaborator")
+            collaborator.stub(:message).and_return(:value)
+            collaborator.message.should eq(:value)
+          end
+        end
+
+        context "specified with a hash passed to #stub" do
+          it "returns the specified value" do
+            collaborator = double("collaborator")
+            collaborator.stub(:message_1 => :value_1, :message_2 => :value_2)
+            collaborator.message_1.should eq(:value_1)
+            collaborator.message_2.should eq(:value_2)
+          end
+        end
+
+        context "specified with a hash passed to #double" do
+          it "returns the specified value" do
+            collaborator = double("collaborator",
+              :message_1 => :value_1,
+              :message_2 => :value_2
+            )
+            collaborator.message_1.should eq(:value_1)
+            collaborator.message_2.should eq(:value_2)
+          end
+        end
+      end
+      """
+    When I run `rspec example_spec.rb`
+    Then the examples should all pass

data/support/gems/rspec-mocks-2.11.1/features/method_stubs/stub_chain.feature

@@ -0,0 +1,51 @@
+Feature: stub a chain of methods
+
+  Use the `stub_chain` method to stub a chain of two or more methods in one
+  statement.  Method chains are considered a design smell, but it's not really
+  the method chain itself that is the problem - it's the dependency chain
+  represented by a chain of messages to different objects:
+
+      foo.get_bar.get_baz
+
+  This is a Law of Demeter violation if `get_bar` returns an object other than
+  `foo`, and `get_baz` returns yet another object.
+
+  Fluent interfaces look similar from a caller's perspective, but don't
+  represent a dependency chain (the caller depends only on the object it is
+  calling). Consider this common example from Ruby on Rails:
+
+      Article.recent.by(current_user)
+
+  The `recent` and `by` methods return the same object, so this is not a Law of
+  Demeter violation.
+
+  Scenario: stub a chain of methods
+    Given a file named "stub_chain_spec.rb" with:
+      """
+      describe "stubbing a chain of methods" do
+        subject { Object.new }
+
+        context "given symbols representing methods" do
+          it "returns the correct value" do
+            subject.stub_chain(:one, :two, :three).and_return(:four)
+            subject.one.two.three.should eq(:four)
+          end
+        end
+
+        context "given a hash at the end" do
+          it "returns the correct value" do
+            subject.stub_chain(:one, :two, :three => :four)
+            subject.one.two.three.should eq(:four)
+          end
+        end
+
+        context "given a string of methods separated by dots" do
+          it "returns the correct value" do
+            subject.stub_chain("one.two.three").and_return(:four)
+            subject.one.two.three.should eq(:four)
+          end
+        end
+      end
+      """
+    When I run `rspec stub_chain_spec.rb`
+    Then the examples should all pass

data/support/gems/rspec-mocks-2.11.1/features/method_stubs/stub_implementation.feature

@@ -0,0 +1,26 @@
+Feature: stub with substitute implementation
+
+  You can stub an implementation of a method (a.k.a. fake) by passing a block
+  to the `stub` method.
+  
+  Scenario: stub implementation
+    Given a file named "stub_implementation_spec.rb" with:
+      """
+      describe "a stubbed implementation" do
+        it "works" do
+          object = Object.new
+          object.stub(:foo) do |arg|
+            if arg == :this
+              "got this"
+            elsif arg == :that
+              "got that"
+            end
+          end
+          
+          object.foo(:this).should eq("got this")
+          object.foo(:that).should eq("got that")
+        end
+      end
+      """
+    When I run `rspec stub_implementation_spec.rb`
+    Then the output should contain "1 example, 0 failures"

data/support/gems/rspec-mocks-2.11.1/features/method_stubs/to_ary.feature

@@ -0,0 +1,47 @@
+Feature: double handling to_ary
+
+  Ruby implicitly sends `to_ary` to all of the objects in an `Array` when the
+  array receives `flatten`:
+
+      [obj].flatten # => obj.to_ary
+
+  If `to_ary` raises a `NoMethodError`, Ruby sees that the object can not be coerced
+  into an array and moves on to the next object.
+
+  To support this, an RSpec double will raise a NoMethodError when it receives
+  `to_ary` _even if it is set `as_null_object`_, unless `to_ary` is explicitly
+  stubbed.
+
+  Scenario: double receiving to_ary
+    Given a file named "example.rb" with:
+      """
+      describe "#to_ary" do
+        shared_examples "to_ary" do
+          it "raises a NoMethodError" do
+            expect { obj.to_ary }.to raise_error(NoMethodError)
+          end
+
+          it "can be overridden with a stub" do
+            obj.stub(:to_ary) { :non_nil_value }
+            obj.to_ary.should be(:non_nil_value)
+          end
+
+          it "supports Array#flatten" do
+            obj = double('foo')
+            [obj].flatten.should eq([obj])
+          end
+        end
+
+        context "sent to a double as_null_object" do
+          let(:obj) { double('obj').as_null_object }
+          include_examples "to_ary"
+        end
+
+        context "sent to a double without as_null_object" do
+          let(:obj) { double('obj') }
+          include_examples "to_ary"
+        end
+      end
+     """
+    When I run `rspec example.rb`
+    Then the examples should all pass

data/support/gems/rspec-mocks-2.11.1/features/outside_rspec/configuration.feature

@@ -0,0 +1,82 @@
+Feature: configure any test framework to use rspec-mocks
+
+  Test frameworks that want to use rspec-mocks can use
+  RSpec::Mocks::setup(self) to hook into rspec-mocks. Doing so adds the
+  following:
+
+    To the object passed to setup:
+
+      double # creates a test double
+      mock   # creates a test double
+      stub   # creates a test double
+
+    To every object in the system:
+
+      should_receive
+      should_not_receive
+      stub
+      
+  In order to give control to the consuming framework, none of these facilities
+  are added until RSpec::Mocks::setup(self) is called. Simply requiring
+  'rspec/mocks' is not sufficient. 
+
+  NOTICE: the stub() method that is added to the object passed to setup is not
+  the same stub() method that is added to every other object.
+
+  Scenario: RSpec::Mocks::setup(object) adds double, mock, and stub methods to the submitted object
+    Given a file named "foo.rb" with:
+      """
+      require 'rspec/mocks'
+
+      class CodeExample
+        def init
+          RSpec::Mocks::setup(self)
+        end
+      end
+
+      example = CodeExample.new
+      example.init
+
+      puts example.respond_to?(:double)
+      puts example.respond_to?(:mock)
+      puts example.respond_to?(:stub)
+      """
+
+    When I run `ruby foo.rb`
+    Then the output should contain "true"
+    But  the output should not contain "false"
+
+  Scenario: RSpec::Mocks::setup(anything) adds methods to Object
+    Given a file named "foo.rb" with:
+      """
+      require 'rspec/mocks'
+
+      RSpec::Mocks::setup(Object.new)
+
+      obj = Object.new
+
+      puts obj.respond_to?(:should_receive)
+      puts obj.respond_to?(:should_not_receive)
+      puts obj.respond_to?(:stub)
+      """
+
+    When I run `ruby foo.rb`
+    Then the output should contain "true"
+    But  the output should not contain "false"
+
+  Scenario: require "rspec/mocks" does not add methods to Object
+    Given a file named "foo.rb" with:
+      """
+      require 'rspec/mocks'
+
+      obj = Object.new
+
+      puts obj.respond_to?(:should_receive)
+      puts obj.respond_to?(:should_not_receive)
+      puts obj.respond_to?(:stub)
+      """
+
+    When I run `ruby foo.rb`
+    Then the output should contain "false"
+    But  the output should not contain "true"
+

data/support/gems/rspec-mocks-2.11.1/features/outside_rspec/standalone.feature

@@ -0,0 +1,32 @@
+Feature: standalone
+
+  require "rspec/mocks/standalone" to expose the mock framework
+  outside the RSpec environment. This is especially useful for
+  exploring rspec-mocks in irb.
+
+  Scenario: method stub outside rspec
+    Given a file named "example.rb" with:
+      """
+      require "rspec/mocks/standalone"
+
+      greeter = double("greeter")
+      greeter.stub(:say_hi) { "Hello!" }
+      puts greeter.say_hi
+      """
+    When I run `ruby example.rb`
+    Then the output should contain "Hello!"
+
+  Scenario: message expectation outside rspec
+    Given a file named "example.rb" with:
+      """
+      require "rspec/mocks/standalone"
+
+      greeter = double("greeter")
+      greeter.should_receive(:say_hi)
+
+      RSpec::Mocks.verify
+      """
+    When I run `ruby example.rb`
+    Then the output should contain "say_hi(any args) (RSpec::Mocks::MockExpectationError)"
+    Then the output should contain "expected: 1 time"
+    Then the output should contain "received: 0 times"

data/support/gems/rspec-mocks-2.11.1/features/step_definitions/additional_cli_steps.rb

@@ -0,0 +1,4 @@
+Then /^the example(?:s)? should(?: all)? pass$/ do
+  step %q{the output should contain "0 failures"}
+  step %q{the exit status should be 0}
+end

data/support/gems/rspec-mocks-2.11.1/features/stubbing_constants/README.md

@@ -0,0 +1,62 @@
+## Stubbing Constants
+
+Support is provided for stubbing constants. Like with method stubs, the
+stubbed constants will be restored to their original state when an
+example completes.
+
+``` ruby
+stub_const("Foo", fake_foo)
+Foo # => fake_foo
+```
+
+Stubbed constant names must be fully qualified; the current module
+nesting is not considered.
+
+``` ruby
+module MyGem
+  class SomeClass; end
+end
+
+module MyGem
+  describe "Something" do
+    let(:fake_class) { Class.new }
+
+    it "accidentally stubs the wrong constant" do
+      # this stubs ::SomeClass (in the top-level namespace),
+      # not MyGem::SomeClass like you probably mean.
+      stub_const("SomeClass", fake_class)
+    end
+
+    it "stubs the right constant" do
+      stub_const("MyGem::SomeClass", fake_class)
+    end
+  end
+end
+```
+
+When you stub a constant that is a module or a class, nested
+constants on the original module or class are not transferred
+by default, but you can use the `:transfer_nested_constants`
+option to tell rspec-mocks to transfer them:
+
+``` ruby
+class CardDeck
+  SUITS = [:Spades, :Diamonds, :Clubs, :Hearts]
+  NUM_CARDS = 52
+end
+
+fake_class = Class.new
+stub_const("CardDeck", fake_class)
+CardDeck # => fake_class
+CardDeck::SUITS # => raises uninitialized constant error
+CardDeck::NUM_CARDS # => raises uninitialized constant error
+
+stub_const("CardDeck", fake_class, :transfer_nested_constants => true)
+CardDeck::SUITS # => [:Spades, :Diamonds, :Clubs, :Hearts]
+CardDeck::NUM_CARDS # => 52
+
+stub_const("CardDeck", fake_class, :transfer_nested_constants => [:SUITS])
+CardDeck::SUITS # => [:Spades, :Diamonds, :Clubs, :Hearts]
+CardDeck::NUM_CARDS # => raises uninitialized constant error
+```
+

data/support/gems/rspec-mocks-2.11.1/features/stubbing_constants/stub_defined_constant.feature

@@ -0,0 +1,79 @@
+Feature: Stub Defined Constant
+
+  Use `stub_const` to stub constants. When the constant is already defined,
+  the stubbed value will replace the original value for the duration of the
+  example.
+
+  Scenario: Stub top-level constant
+    Given a file named "stub_const_spec.rb" with:
+      """ruby
+      FOO = 7
+
+      describe "stubbing FOO" do
+        it "can stub FOO with a different value" do
+          stub_const("FOO", 5)
+          FOO.should eq(5)
+        end
+
+        it "restores the stubbed constant when the example completes" do
+          FOO.should eq(7)
+        end
+      end
+      """
+    When I run `rspec stub_const_spec.rb`
+    Then the examples should all pass
+
+  Scenario: Stub nested constant
+    Given a file named "stub_const_spec.rb" with:
+      """ruby
+      module MyGem
+        class SomeClass
+          FOO = 7
+        end
+      end
+
+      module MyGem
+        describe SomeClass do
+          it "stubs the nested constant when it is fully qualified" do
+            stub_const("MyGem::SomeClass::FOO", 5)
+            SomeClass::FOO.should eq(5)
+          end
+        end
+      end
+      """
+    When I run `rspec stub_const_spec.rb`
+    Then the examples should all pass
+
+  Scenario: Transfer nested constants
+    Given a file named "stub_const_spec.rb" with:
+      """ruby
+      module MyGem
+        class SomeClass
+          FOO = 7
+        end
+      end
+
+      module MyGem
+        describe SomeClass do
+          let(:fake_class) { Class.new }
+
+          it "does not transfer nested constants by default" do
+            stub_const("MyGem::SomeClass", fake_class)
+            expect { SomeClass::FOO }.to raise_error(NameError)
+          end
+
+          it "transfers nested constants when using :transfer_nested_constants => true" do
+            stub_const("MyGem::SomeClass", fake_class, :transfer_nested_constants => true)
+            SomeClass::FOO.should eq(7)
+          end
+
+          it "can specify a list of nested constants to transfer" do
+            stub_const("MyGem::SomeClass", fake_class, :transfer_nested_constants => [:FOO])
+            SomeClass::FOO.should eq(7)
+          end
+        end
+      end
+      """
+    When I run `rspec stub_const_spec.rb`
+    Then the examples should all pass
+