rspec-core 2.0.0.a1

data/features-pending/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:
+      """
+      Rspec::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 match "1 example, 0 failures"
+    And  the stdout should match "should be bigger than 4"

data/features-pending/mocks/mix_stubs_and_mocks.feature

@@ -0,0 +1,22 @@
+Feature: Spec and test 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 match "expected :foo with (\"first\") but received it with ([\"second\"], [\"third\"])"

data/features-pending/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 match "1 example, 0 failures"

data/features-pending/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 match "1 example, 0 failures, 1 pending"
+    And the stdout should match "Not Yet Implemented"
+    And the stdout should match "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 match "1 example, 0 failures, 1 pending"
+    And the stdout should match "Not Yet Implemented"
+    And the stdout should match "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 match "1 example, 0 failures, 1 pending"
+    And the stdout should match "(something else getting finished)"
+    And the stdout should match "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 match "1 example, 0 failures, 1 pending"
+    And the stdout should match "(something else getting finished)"
+    And the stdout should match "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 match "1 example, 1 failure"
+    And the stdout should match "FIXED"
+    And the stdout should match "Expected pending 'something else getting finished' to fail. No Error was raised."
+    And the stdout should match "pending_with_passing_block_spec.rb:3"

data/features-pending/runner/specify_line_number.feature

@@ -0,0 +1,32 @@
+Feature: run specific examples by line number
+
+  In order to run a single example from command line
+  RSpec allows you to specify the line number of the example(s) to run
+
+  Scenario: --line syntax on single example
+    Given a file named "example_spec.rb" with:
+      """
+      describe "an example" do
+        it "has not yet been implemented"
+        it "has been implemented" do
+          true
+        end
+      end
+      """
+    When I run "spec example_spec.rb --line 2"
+    Then the stdout should match "1 example, 0 failures, 1 pending"
+    And the stdout should match "example_spec.rb:2"
+
+  Scenario: colon line syntax on single example
+    Given a file named "example_spec.rb" with:
+      """
+      describe "an example" do
+        it "has not yet been implemented"
+        it "has been implemented" do
+          true
+        end
+      end
+      """
+    When I run "spec example_spec.rb:2"
+    Then the stdout should match "1 example, 0 failures, 1 pending"
+    And the stdout should match "example_spec.rb:2"

data/features/before_and_after_blocks/before_and_after_blocks.feature

@@ -0,0 +1,169 @@
+Feature: before and after blocks
+
+  As a developer using RSpec
+  I want to execute arbitrary code before and after each example
+  So that I can control the environment in which it is run
+
+    This is supported by the before and after methods which each take a symbol
+    indicating the scope, and a block of code to execute.
+
+    before(:each) blocks are run before each example
+    before(:all) blocks are run once before all of the examples in a group
+    before(:suite) blocks are run once before the entire suite
+
+    after(:each) blocks are run after each example
+    after(:all) blocks are run once after all of the examples in a group
+    after(:suite) blocks are run once after the entire suite
+
+    Before and after blocks are called in the following order:
+      before suite
+      before all
+      before each
+      after each
+      after all
+      after suite
+
+    Before and after blocks can be defined in the example groups to which they
+    apply or in a configuration. When defined in a configuration, they can be
+    applied to all groups or subsets of all groups defined by example group
+    types.
+
+  Scenario: define before(:each) block in example group
+    Given a file named "before_each_in_example_group_spec.rb" with:
+      """
+      class Thing
+        def widgets
+          @widgets ||= []
+        end
+      end
+
+      describe Thing do
+        before(:each) do
+          @thing = Thing.new
+        end
+
+        describe "initialized in before(:each)" do
+          it "has 0 widgets" do
+            @thing.should have(0).widgets
+          end
+
+          it "can get accept new widgets" do
+            @thing.widgets << Object.new
+          end
+
+          it "does not share state across examples" do
+            @thing.should have(0).widgets
+          end
+        end
+      end
+      """
+    When I run "rspec before_each_in_example_group_spec.rb"
+    Then the stdout should match "3 examples, 0 failures"
+
+  Scenario: define before(:all) block in example group
+    Given a file named "before_all_in_example_group_spec.rb" with:
+      """
+      class Thing
+        def widgets
+          @widgets ||= []
+        end
+      end
+  
+      describe Thing do
+        before(:all) do
+          @thing = Thing.new
+        end
+  
+        describe "initialized in before(:all)" do
+          it "has 0 widgets" do
+            @thing.should have(0).widgets
+          end
+  
+          it "can get accept new widgets" do
+            @thing.widgets << Object.new
+          end
+  
+          it "shares state across examples" do
+            @thing.should have(1).widgets
+          end
+        end
+      end
+      """
+    When I run "rspec before_all_in_example_group_spec.rb"
+    Then the stdout should match "3 examples, 0 failures"
+
+  @wip
+  Scenario: define before and after blocks in configuration
+    Given a file named "befores_in_configuration_spec.rb" with:
+      """
+      Rspec::Core.configure do |config|
+        config.before(:suite) do
+          $before_suite = "before suite"
+        end
+        config.before(:each) do
+          @before_each = "before each"
+        end
+        config.before(:all) do
+          @before_all = "before all"
+        end
+      end
+  
+      describe "stuff in before blocks" do
+        describe "with :suite" do
+          it "should be available in the example" do
+            $before_suite.should == "before suite"
+          end
+        end
+        describe "with :all" do
+          it "should be available in the example" do
+            @before_all.should == "before all"
+          end
+        end
+        describe "with :each" do
+          it "should be available in the example" do
+            @before_each.should == "before each"
+          end
+        end
+      end
+      """
+    When I run "spec befores_in_configuration_spec.rb"
+    Then the stdout should match "3 examples, 0 failures"
+
+  @wip
+  Scenario: before/after blocks are run in order
+    Given a file named "ensure_block_order_spec.rb" with:
+      """
+      Rspec::Core.configure do |config|
+        config.before(:suite) do
+          puts "before suite"
+        end
+        config.after(:suite) do
+          puts "after suite"
+        end
+      end
+  
+      describe "before and after callbacks" do
+        before(:all) do
+          puts "before all"
+        end
+  
+        before(:each) do
+          puts "before each"
+        end
+  
+        after(:each) do
+          puts "after each"
+        end
+  
+        after(:all) do
+          puts "after all"
+        end
+  
+        it "gets run in order" do
+  
+        end
+      end
+      """
+    When I run "spec ensure_block_order_spec.rb"
+    Then the stdout should match /before suite\nbefore all\nbefore each\nafter each\n\.after all\n.*after suite/m
+  

data/features/expectations/customized_message.feature

@@ -0,0 +1,54 @@
+Feature: customized message
+
+  In order to get the feedback I want
+  As an RSpec user
+  I want to customize the failure message per example
+  
+  Scenario: one additional method
+    Given a file named "node_spec.rb.rb" with:
+      """
+      class Node
+        def initialize(state=:waiting)
+          @state = state
+        end
+        def state
+          @state
+        end
+        def waiting?
+          @state == :waiting
+        end
+        def started?
+          @state == :started
+        end
+        def start
+          @state = :started
+        end
+      end
+      
+      describe "a new Node" do
+        it "should be waiting" do
+          node = Node.new(:started) #start w/ started to trigger failure
+          node.should be_waiting, "node.state: #{node.state} (first example)"
+        end
+        
+        it "should not be started" do
+          node = Node.new(:started) #start w/ started to trigger failure
+          node.should_not be_started, "node.state: #{node.state} (second example)"
+        end
+      end
+      
+      describe "node.start" do
+        it "should change the state" do
+          node = Node.new(:started) #start w/ started to trigger failure
+          lambda {node.start}.should change{node.state}, "expected a change"
+        end
+      end
+      
+      """
+    When I run "spec node_spec.rb.rb --format specdoc"
+    Then the stdout should match "3 examples, 3 failures"
+    And  the stdout should not match "to return true, got false"
+    And  the stdout should not match "to return false, got true"
+    And  the stdout should match "node.state: started (first example)"
+    And  the stdout should match "node.state: started (second example)"
+    And  the stdout should match "expected a change"

data/features/matchers/define_matcher_outside_rspec.feature

@@ -0,0 +1,39 @@
+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:
+      """
+      $:.unshift File.join(File.dirname(__FILE__), "/../../lib")
+      require 'test/unit'
+      require 'rspec/expectations'
+      
+      Rspec::Matchers.define :be_a_multiple_of do |expected|
+        match do |actual|
+          actual % expected == 0
+        end
+      end
+      
+      class Test::Unit::TestCase
+        include Rspec::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 match "expected 9 to be a multiple of 4"
+    And the stdout should match "2 tests, 0 assertions, 1 failures, 0 errors"