pupu 0.0.1

data/vendor/rspec/features/matchers/define_matcher_outside_rspec.feature

@@ -0,0 +1,38 @@
+Feature: define matcher outside rspec
+
+  In order to express my domain clearly in my code examples
+  As a non-rspec user
+  I want a shortcut to define custom matchers
+
+  Scenario: define a matcher with default messages
+    Given a file named "test_multiples.rb" with:
+      """
+      require 'test/unit'
+      require 'spec/expectations'
+      
+      Spec::Matchers.define :be_a_multiple_of do |expected|
+        match do |actual|
+          actual % expected == 0
+        end
+      end
+      
+      class Test::Unit::TestCase
+        include Spec::Matchers
+      end
+      
+      class TestMultiples < Test::Unit::TestCase
+      
+        def test_9_should_be_a_multiple_of_3
+          9.should be_a_multiple_of(3)
+        end
+
+        def test_9_should_be_a_multiple_of_4
+          9.should be_a_multiple_of(4)
+        end
+        
+      end
+      """
+    When I run "ruby test_multiples.rb"
+    Then the exit code should be 256
+    And the stdout should include "expected 9 to be a multiple of 4"
+    And the stdout should include "2 tests, 0 assertions, 1 failures, 0 errors"

data/vendor/rspec/features/matchers/define_matcher_with_fluent_interface.feature

@@ -0,0 +1,27 @@
+Feature: define matcher
+
+  In order to express my domain clearly in my code examples
+  As an RSpec user
+  I want to define matchers with fluent interfaces
+  
+  Scenario: one additional method
+    Given a file named "between_spec.rb" with:
+      """
+      Spec::Matchers.define :be_bigger_than do |first|
+        def but_smaller_than(second)
+          @second = second
+          self
+        end
+        
+        match do |actual|
+          (actual > first) && (actual < @second)
+        end
+      end
+
+      describe 5 do
+        it { should be_bigger_than(4).but_smaller_than(6) }
+      end
+      """
+    When I run "spec between_spec.rb --format specdoc"
+    Then the stdout should include "1 example, 0 failures"
+    And  the stdout should include "should be bigger than 4"

data/vendor/rspec/features/matchers/define_wrapped_matcher.feature

@@ -0,0 +1,29 @@
+Feature: define wrapped matcher
+
+  In order to reuse existing matchers
+  As an RSpec user
+  I want to define matchers that wrap other matchers
+  
+  Scenario: one additional method
+    Given a file named "new_model_spec.rb" with:
+      """
+      Spec::Matchers.define :have_tag do |tag|
+        match do |markup|
+          markup =~ /<#{tag}>.*<\/#{tag}>/
+        end
+      end
+      
+      Spec::Matchers.define :have_button do
+        match do |markup|
+          markup.should have_tag('button')
+        end
+      end
+      
+      describe "some markup" do
+        it "has a button" do
+          "<button>Label</button>".should have_button
+        end
+      end
+      """
+    When I run "spec new_model_spec.rb --format specdoc"
+    Then the stdout should include "1 example, 0 failures"

data/vendor/rspec/features/matchers/match_unless_raises.feature

@@ -0,0 +1,60 @@
+Feature: match unless raises
+
+  In order, primarily, to reuse existing test/unit assertions
+  As an RSpec user
+  I want to define matchers that wrap a statement that raises an error on failure
+
+  Background:
+    Given a file named "example.rb" with:
+      """
+      require 'test/unit/assertions'
+
+      Spec::Matchers.define :be_the_same_as do |expected|
+        extend Test::Unit::Assertions
+        match_unless_raises Test::Unit::AssertionFailedError do |actual|
+          assert_equal expected, actual
+        end
+      end
+      """
+  
+  Scenario: passing examples
+    Given a file named "match_unless_raises_spec.rb" with:
+      """
+      require 'example.rb'
+
+      describe 4 do
+        it "is 4" do
+          4.should be_the_same_as(4)
+        end
+      end
+
+      describe 5 do
+        it "is not 4" do
+          5.should_not be_the_same_as(4)
+        end
+      end
+      """
+    When I run "spec match_unless_raises_spec.rb"
+    Then the stdout should include "2 examples, 0 failures"
+
+  Scenario: failing examples
+    Given a file named "match_unless_raises_spec.rb" with:
+      """
+      require 'example.rb'
+
+      describe 4 do
+        it "is 4" do
+          # intentionally fail
+          4.should_not be_the_same_as(4)
+        end
+      end
+
+      describe 5 do
+        it "is not 4" do
+          # intentionally fail
+          5.should be_the_same_as(4)
+        end
+      end
+      """
+    When I run "spec match_unless_raises_spec.rb"
+    Then the stdout should include "2 examples, 2 failures"

data/vendor/rspec/features/matchers/match_unless_raises_unexpected_error.feature

@@ -0,0 +1,39 @@
+Feature: match unless raises with an unexpected error
+
+  In order to know when a match_unless_raises block raises an unexpected error
+  As an RSpec user
+  I want the error to bubble up
+
+  Background:
+    Given a file named "example.rb" with:
+      """
+      Spec::Matchers.define :be_the_same_as do |expected|
+        match_unless_raises SyntaxError do |actual|
+          raise "unexpected error"
+        end
+      end
+      """
+  
+  Scenario: failing examples
+    Given a file named "match_unless_raises_spec.rb" with:
+      """
+      require 'example.rb'
+
+      describe 4 do
+        it "is 4" do
+          # intentionally fail
+          4.should_not be_the_same_as(4)
+        end
+      end
+
+      describe 5 do
+        it "is not 4" do
+          # intentionally fail
+          5.should be_the_same_as(4)
+        end
+      end
+      """
+    When I run "spec match_unless_raises_spec.rb"
+    Then the stdout should include "2 examples, 2 failures"
+    Then the stdout should include "unexpected error"
+  

data/vendor/rspec/features/mock_framework_integration/use_flexmock.feature

@@ -0,0 +1,27 @@
+Feature: mock with flexmock
+
+  As an RSpec user who prefers flexmock
+  I want to be able to use flexmock without rspec mocks interfering
+
+  Scenario: Mock with flexmock
+    Given a file named "flexmock_example_spec.rb" with:
+      """
+      Spec::Runner.configure do |config|
+        config.mock_with :flexmock
+      end
+
+      describe "plugging in flexmock" do
+        it "allows flexmock to be used" do
+          target = Object.new
+          flexmock(target).should_receive(:foo).once
+          target.foo
+        end
+
+        it "does not include rspec mocks" do
+          Spec.const_defined?(:Mocks).should be_false
+        end
+      end
+      """
+    When I run "spec flexmock_example_spec.rb"
+    Then the exit code should be 0
+    And the stdout should include "2 examples, 0 failures"

data/vendor/rspec/features/mock_framework_integration/use_mocha.feature

@@ -0,0 +1,27 @@
+Feature: mock with mocha
+
+  As an RSpec user who prefers mocha
+  I want to be able to use mocha without rspec mocks interfering
+
+  Scenario: Mock with mocha
+    Given a file named "mocha_example_spec.rb" with:
+      """
+      Spec::Runner.configure do |config|
+        config.mock_with :mocha
+      end
+
+      describe "plugging in mocha" do
+        it "allows mocha to be used" do
+          target = Object.new
+          target.expects(:foo).once
+          target.foo
+        end
+
+        it "does not include rspec mocks" do
+          Spec.const_defined?(:Mocks).should be_false
+        end
+      end
+      """
+    When I run "spec mocha_example_spec.rb"
+    Then the exit code should be 0
+    And the stdout should include "2 examples, 0 failures"

data/vendor/rspec/features/mock_framework_integration/use_rr.feature

@@ -0,0 +1,27 @@
+Feature: mock with rr
+
+  As an RSpec user who prefers rr
+  I want to be able to use rr without rspec mocks interfering
+
+  Scenario: Mock with rr
+    Given a file named "rr_example_spec.rb" with:
+      """
+      Spec::Runner.configure do |config|
+        config.mock_with :rr
+      end
+
+      describe "plugging in rr" do
+        it "allows rr to be used" do
+          target = Object.new
+          mock(target).foo
+          target.foo
+        end
+
+        it "does not include rspec mocks" do
+          Spec.const_defined?(:Mocks).should be_false
+        end
+      end
+      """
+    When I run "spec rr_example_spec.rb"
+    Then the exit code should be 0
+    And the stdout should include "2 examples, 0 failures"

data/vendor/rspec/features/mocks/block_local_expectations.feature

@@ -0,0 +1,62 @@
+Feature: block local expectations
+
+  In order to set message expectations on ...
+  As an RSpec user
+  I want to configure the evaluation context
+
+  Background:
+    Given a file named "account.rb" with:
+      """
+      class Account
+        def self.create
+          yield new
+        end
+
+        def opening_balance(amount, currency)
+        end
+      end
+      """
+
+  Scenario: passing example
+    Given a file named "account_dsl.rb" with:
+      """
+      require 'spec_helper'
+      require 'account'
+
+      describe "account DSL" do
+        it " .... " do
+          account = Account.new
+          Account.should_receive(:create).and_yield do |account|
+            account.should_receive(:opening_balance).with(100, :USD)
+          end
+          Account.create do
+            opening_balance 100, :USD
+          end
+        end
+      end
+      """
+    When I run "spec account_dsl.rb"
+    Then the stdout should include "1 example, 0 failures"
+    
+  Scenario: failing example
+    
+    Given a file named "account_dsl.rb" with:
+      """
+      require 'spec_helper'
+      require 'account'
+
+      describe "account DSL" do
+        it " .... " do
+          account = Account.new
+          Account.should_receive(:create).and_yield do |account|
+            account.should_receive(:opening_balance).with(100, :USD)
+          end
+          Account.create do
+            # opening_balance is not called here
+          end
+        end
+      end
+      """
+
+    When I run "spec account_dsl.rb"
+    Then the stdout should include "1 example, 1 failure"

data/vendor/rspec/features/mocks/mix_stubs_and_mocks.feature

@@ -0,0 +1,22 @@
+Feature: stub and mock together
+
+  As an RSpec user
+  I want to use stubs and mocks together
+
+  Scenario: stub in before
+    Given a file named "stub_and_mocks_spec.rb" with:
+      """
+      describe "a stub in before" do
+        before(:each) do
+          @messenger = mock('messenger').as_null_object
+        end
+
+        it "a" do
+          @messenger.should_receive(:foo).with('first')
+          @messenger.foo('second')
+          @messenger.foo('third')
+        end
+      end
+      """
+    When I run "spec stub_and_mocks_spec.rb --format nested"
+    Then the stdout should include "received :foo with unexpected arguments\n  expected: (\"first\")\n       got: ([\"second\"], [\"third\"])"

data/vendor/rspec/features/mocks/stub_implementation.feature

@@ -0,0 +1,26 @@
+Feature: stub implementation
+
+  As an rspec user, I want to stub a complete implementation, not just a
+  return value.
+  
+  Scenario: stub implementation
+    Given a file named "stub_implementation.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 == "got this"
+          object.foo(:that).should == "got that"
+        end
+      end
+      """
+    When I run "spec stub_implementation.rb"
+    Then the stdout should include "1 example, 0 failures"

data/vendor/rspec/features/pending/pending_examples.feature

@@ -0,0 +1,81 @@
+Feature: pending examples
+
+  RSpec offers three ways to indicate that an example is disabled pending
+  some action.
+
+  Scenario: pending implementation
+    Given a file named "example_without_block_spec.rb" with:
+      """
+      describe "an example" do
+        it "has not yet been implemented"
+      end
+      """
+    When I run "spec example_without_block_spec.rb"
+    Then the exit code should be 0
+    And the stdout should include "1 example, 0 failures, 1 pending"
+    And the stdout should include "Not Yet Implemented"
+    And the stdout should include "example_without_block_spec.rb:2"
+
+  Scenario: pending implementation with spec/test/unit
+    Given a file named "example_without_block_spec.rb" with:
+      """
+      require 'spec/test/unit'
+      describe "an example" do
+        it "has not yet been implemented"
+      end
+      """
+    When I run "spec example_without_block_spec.rb"
+    Then the exit code should be 0
+    And the stdout should include "1 example, 0 failures, 1 pending"
+    And the stdout should include "Not Yet Implemented"
+    And the stdout should include "example_without_block_spec.rb:3"
+
+  Scenario: pending any arbitary reason, with no block
+    Given a file named "pending_without_block_spec.rb" with:
+      """
+      describe "an example" do
+        it "is implemented but waiting" do
+          pending("something else getting finished")
+        end
+      end
+      """
+    When I run "spec pending_without_block_spec.rb"
+    Then the exit code should be 0
+    And the stdout should include "1 example, 0 failures, 1 pending"
+    And the stdout should include "(something else getting finished)"
+    And the stdout should include "pending_without_block_spec.rb:2"
+
+  Scenario: pending any arbitary reason, with a block that fails
+    Given a file named "pending_with_failing_block_spec.rb" with:
+      """
+      describe "an example" do
+        it "is implemented but waiting" do
+          pending("something else getting finished") do
+            raise "this is the failure"
+          end
+        end
+      end
+      """
+    When I run "spec pending_with_failing_block_spec.rb"
+    Then the exit code should be 0
+    And the stdout should include "1 example, 0 failures, 1 pending"
+    And the stdout should include "(something else getting finished)"
+    And the stdout should include "pending_with_failing_block_spec.rb:2"
+
+  Scenario: pending any arbitary reason, with a block that passes
+    Given a file named "pending_with_passing_block_spec.rb" with:
+      """
+      describe "an example" do
+        it "is implemented but waiting" do
+          pending("something else getting finished") do
+            true.should be(true)
+          end
+        end
+      end
+      """
+    When I run "spec pending_with_passing_block_spec.rb"
+    Then the exit code should be 256
+    And the stdout should include "1 example, 1 failure"
+    And the stdout should include "FIXED"
+    And the stdout should include "Expected pending 'something else getting finished' to fail. No Error was raised."
+    And the stdout should include "pending_with_passing_block_spec.rb:3"