gem_repackager 0.1.0

data/support/gems/rspec-core-2.11.1/features/metadata/current_example.feature

@@ -0,0 +1,17 @@
+Feature: current example
+
+  You can reference the example object, and access its metadata, using
+  the `example` method within an example.
+
+  Scenario: access the example object from within an example
+    Given a file named "spec/example_spec.rb" with:
+      """
+      describe "an example" do
+        it "knows itself as example" do
+          example.description.should eq("knows itself as example")
+        end
+      end
+      """
+    When I run `rspec spec/example_spec.rb`
+    Then the example should pass
+

data/support/gems/rspec-core-2.11.1/features/metadata/described_class.feature

@@ -0,0 +1,17 @@
+Feature: described class
+
+  If the first argument to the outermost example group is a class, the class is
+  exposed to each example via the described_class() method.
+
+  Scenario: access the described class from the example
+    Given a file named "spec/example_spec.rb" with:
+      """
+      describe Fixnum do
+        it "is available as described_class" do
+          described_class.should eq(Fixnum)
+        end
+      end
+      """
+    When I run `rspec spec/example_spec.rb`
+    Then the example should pass
+

data/support/gems/rspec-core-2.11.1/features/metadata/user_defined.feature

@@ -0,0 +1,113 @@
+Feature: User-defined metadata
+
+  You can attach user-defined metadata to any example group or example.
+  Pass a hash as the last argument (before the block) to `describe`,
+  `context` or `it`.  RSpec supports many configuration options that apply
+  only to certain examples or groups based on the metadata.
+
+  Metadata defined on an example group is available (and can be overridden)
+  by any sub-group or from any example in that group or a sub-group.
+
+  In addition, there is a configuration option (which will be the default
+  behavior in RSpec 3) that allows you to specify metadata using just
+  symbols:
+
+  ```ruby
+  RSpec.configure do |c|
+    c.treat_symbols_as_metadata_keys_with_true_values = true
+  end
+  ```
+
+  Each symbol passed as an argument to `describe`, `context` or `it` will
+  be a key in the metadata hash, with a corresponding value of `true`.
+
+  Scenario: define group metadata using a hash
+    Given a file named "define_group_metadata_with_hash_spec.rb" with:
+      """
+      describe "a group with user-defined metadata", :foo => 17 do
+        it 'has access to the metadata in the example' do
+          example.metadata[:foo].should eq(17)
+        end
+
+        it 'does not have access to metadata defined on sub-groups' do
+          example.metadata.should_not include(:bar)
+        end
+
+        describe 'a sub-group with user-defined metadata', :bar => 12 do
+          it 'has access to the sub-group metadata' do
+            example.metadata[:foo].should eq(17)
+          end
+
+          it 'also has access to metadata defined on parent groups' do
+            example.metadata[:bar].should eq(12)
+          end
+        end
+      end
+      """
+    When I run `rspec define_group_metadata_with_hash_spec.rb`
+    Then the examples should all pass
+
+  Scenario: define example metadata using a hash
+    Given a file named "define_example_metadata_with_hash_spec.rb" with:
+      """
+      describe "a group with no user-defined metadata" do
+        it 'has an example with metadata', :foo => 17 do
+          example.metadata[:foo].should eq(17)
+          example.metadata.should_not include(:bar)
+        end
+
+        it 'has another example with metadata', :bar => 12, :bazz => 33 do
+          example.metadata[:bar].should eq(12)
+          example.metadata[:bazz].should eq(33)
+          example.metadata.should_not include(:foo)
+        end
+      end
+      """
+    When I run `rspec define_example_metadata_with_hash_spec.rb`
+    Then the examples should all pass
+
+  Scenario: override user-defined metadata
+    Given a file named "override_metadata_spec.rb" with:
+      """
+      describe "a group with user-defined metadata", :foo => 'bar' do
+        it 'can be overridden by an example', :foo => 'bazz' do
+          example.metadata[:foo].should == 'bazz'
+        end
+
+        describe "a sub-group with an override", :foo => 'goo' do
+          it 'can be overridden by a sub-group' do
+            example.metadata[:foo].should == 'goo'
+          end
+        end
+      end
+      """
+    When I run `rspec override_metadata_spec.rb`
+    Then the examples should all pass
+
+  Scenario: less verbose metadata
+    Given a file named "less_verbose_metadata_spec.rb" with:
+      """
+      RSpec.configure do |c|
+        c.treat_symbols_as_metadata_keys_with_true_values = true
+      end
+
+      describe "a group with simple metadata", :fast, :simple, :bug => 73 do
+        it 'has `:fast => true` metadata' do
+          example.metadata[:fast].should == true
+        end
+
+        it 'has `:simple => true` metadata' do
+          example.metadata[:simple].should == true
+        end
+
+        it 'can still use a hash for metadata' do
+          example.metadata[:bug].should eq(73)
+        end
+
+        it 'can define simple metadata on an example', :special do
+          example.metadata[:special].should == true
+        end
+      end
+      """
+    When I run `rspec less_verbose_metadata_spec.rb`
+    Then the examples should all pass

data/support/gems/rspec-core-2.11.1/features/mock_framework_integration/use_any_framework.feature

@@ -0,0 +1,106 @@
+Feature: mock with an alternative framework
+
+  In addition to rspec, mocha, flexmock, and RR, you can choose an alternate
+  framework as the mocking framework. You (or the framework authors) just needs
+  to provide an adapter that hooks RSpec's events into those of the framework.
+
+  A mock framework adapter must expose three methods:
+    
+  * setup_mocks_for_rspec
+    * called before each example is run
+  * verify_mocks_for_rspec 
+    * called after each example is run
+    * this is where message expectation failures should result in an error with
+      the appropriate failure message
+  * teardown_mocks_for_rspec 
+    * called after verify_mocks_for_rspec
+    * use this to clean up resources, restore objects to earlier state, etc
+    * guaranteed to run even if there are failures
+
+  Scenario: Mock with alternate framework
+    Given a file named "expector.rb" with:
+      """
+      class Expector
+        class << self
+          def expectors
+            @expectors ||= []
+          end
+
+          def clear_expectors
+            expectors.clear
+          end
+
+          def verify_expectors
+            expectors.each {|d| d.verify}
+          end
+        end
+
+        def initialize
+          self.class.expectors << self
+        end
+
+        def expectations
+          @expectations ||= []
+        end
+
+        def expect(message)
+          expectations << message.to_s
+        end
+
+        def verify
+          unless expectations.empty?
+            raise expectations.map {|e|
+              "expected #{e}, but it was never received"
+            }.join("\n")
+          end
+        end
+
+      private
+
+        def method_missing(name, *args, &block)
+          expectations.delete(name.to_s)
+        end
+
+      public
+
+        module RSpecAdapter
+          def setup_mocks_for_rspec
+            # no setup necessary
+          end
+
+          def verify_mocks_for_rspec
+            Expector.verify_expectors.each {|d| d.verify}
+          end
+
+          def teardown_mocks_for_rspec
+            Expector.clear_expectors
+          end
+        end
+      end
+      """
+      
+    Given a file named "example_spec.rb" with:
+      """
+      require File.expand_path("../expector", __FILE__)
+
+      RSpec.configure do |config|
+        config.mock_framework = Expector::RSpecAdapter
+      end
+
+      describe Expector do
+        it "passes when message is received" do
+          expector = Expector.new
+          expector.expect(:foo)
+          expector.foo
+        end
+
+        it "fails when message is received" do
+          expector = Expector.new
+          expector.expect(:foo)
+        end
+      end
+      """
+    When I run `rspec example_spec.rb --format doc`
+    Then the exit status should be 1
+    And the output should contain "2 examples, 1 failure" 
+    And the output should contain "fails when message is received (FAILED - 1)" 

data/support/gems/rspec-core-2.11.1/features/mock_framework_integration/use_flexmock.feature

@@ -0,0 +1,96 @@
+Feature: mock with flexmock
+
+  Configure RSpec to use flexmock as shown in the scenarios below.
+
+  Scenario: passing message expectation
+    Given a file named "example_spec.rb" with:
+      """
+      RSpec.configure do |config|
+        config.mock_framework = :flexmock
+      end
+
+      describe "mocking with Flexmock" do
+        it "passes when it should" do
+          receiver = flexmock('receiver')
+          receiver.should_receive(:message).once
+          receiver.message
+        end
+      end
+      """
+    When I run `rspec example_spec.rb`
+    Then the examples should all pass 
+
+  Scenario: failing message expecation
+    Given a file named "example_spec.rb" with:
+      """
+      RSpec.configure do |config|
+        config.mock_framework = :flexmock
+      end
+
+      describe "mocking with Flexmock" do
+        it "fails when it should" do
+          receiver = flexmock('receiver')
+          receiver.should_receive(:message).once
+        end
+      end
+      """
+    When I run `rspec example_spec.rb`
+    Then the output should contain "1 example, 1 failure"
+
+  Scenario: failing message expectation in pending block (remains pending)
+    Given a file named "example_spec.rb" with:
+      """
+      RSpec.configure do |config|
+        config.mock_framework = :flexmock
+      end
+
+      describe "failed message expectation in a pending block" do
+        it "is listed as pending" do
+          pending do
+            receiver = flexmock('receiver')
+            receiver.should_receive(:message).once
+          end
+        end
+      end
+      """
+    When I run `rspec example_spec.rb`
+    Then the output should contain "1 example, 0 failures, 1 pending"
+    And the exit status should be 0
+
+  Scenario: passing message expectation in pending block (fails)
+    Given a file named "example_spec.rb" with:
+      """
+      RSpec.configure do |config|
+        config.mock_framework = :flexmock
+      end
+
+      describe "passing message expectation in a pending block" do
+        it "fails with FIXED" do
+          pending do
+            receiver = flexmock('receiver')
+            receiver.should_receive(:message).once
+            receiver.message
+          end
+        end
+      end
+      """
+    When I run `rspec example_spec.rb`
+    Then the output should contain "FIXED"
+    Then the output should contain "1 example, 1 failure"
+    And the exit status should be 1
+
+  Scenario: accessing RSpec.configuration.mock_framework.framework_name 
+    Given a file named "example_spec.rb" with:
+      """
+      RSpec.configure do |config|
+        config.mock_framework = :flexmock
+      end
+
+      describe "RSpec.configuration.mock_framework.framework_name" do
+        it "returns :flexmock" do
+          RSpec.configuration.mock_framework.framework_name.should eq(:flexmock)
+        end
+      end
+      """
+    When I run `rspec example_spec.rb`
+    Then the examples should all pass 

data/support/gems/rspec-core-2.11.1/features/mock_framework_integration/use_mocha.feature

@@ -0,0 +1,97 @@
+Feature: mock with mocha
+
+  Configure RSpec to use mocha as shown in the scenarios below.
+
+  Scenario: passing message expectation
+    Given a file named "example_spec.rb" with:
+      """
+      RSpec.configure do |config|
+        config.mock_framework = :mocha
+      end
+
+      describe "mocking with RSpec" do
+        it "passes when it should" do
+          receiver = mock('receiver')
+          receiver.expects(:message).once
+          receiver.message
+        end
+      end
+      """
+    When I run `rspec example_spec.rb`
+    Then the examples should all pass 
+
+  Scenario: failing message expecation
+    Given a file named "example_spec.rb" with:
+      """
+      RSpec.configure do |config|
+        config.mock_framework = :mocha
+      end
+
+      describe "mocking with RSpec" do
+        it "fails when it should" do
+          receiver = mock('receiver')
+          receiver.expects(:message).once
+        end
+      end
+      """
+    When I run `rspec example_spec.rb`
+    Then the output should contain "1 example, 1 failure"
+
+  Scenario: failing message expectation in pending block (remains pending)
+    Given a file named "example_spec.rb" with:
+      """
+      RSpec.configure do |config|
+        config.mock_framework = :mocha
+      end
+
+      describe "failed message expectation in a pending block" do
+        it "is listed as pending" do
+          pending do
+            receiver = mock('receiver')
+            receiver.expects(:message).once
+          end
+        end
+      end
+      """
+    When I run `rspec example_spec.rb`
+    Then the output should contain "1 example, 0 failures, 1 pending"
+    And the exit status should be 0
+
+  Scenario: passing message expectation in pending block (fails)
+    Given a file named "example_spec.rb" with:
+      """
+      RSpec.configure do |config|
+        config.mock_framework = :mocha
+      end
+
+      describe "passing message expectation in a pending block" do
+        it "fails with FIXED" do
+          pending do
+            receiver = mock('receiver')
+            receiver.expects(:message).once
+            receiver.message
+          end
+        end
+      end
+      """
+    When I run `rspec example_spec.rb`
+    Then the output should contain "FIXED"
+    Then the output should contain "1 example, 1 failure"
+    And the exit status should be 1
+
+  Scenario: accessing RSpec.configuration.mock_framework.framework_name 
+    Given a file named "example_spec.rb" with:
+      """
+      RSpec.configure do |config|
+        config.mock_framework = :mocha
+      end
+
+      describe "RSpec.configuration.mock_framework.framework_name" do
+        it "returns :mocha" do
+          RSpec.configuration.mock_framework.framework_name.should eq(:mocha)
+        end
+      end
+      """
+    When I run `rspec example_spec.rb`
+    Then the examples should all pass 
+