rspec 1.2.2 → 1.2.3

data/features/example_groups/nested_groups.feature

@@ -4,14 +4,29 @@ Feature: Nested example groups
   I want to nest examples groups
   So that I can better organize my examples
 
-  Scenario: Run with ruby
-    Given the file ../../examples/passing/stack_spec_with_nested_example_groups.rb
-    When I run it with the ruby interpreter -fs
-    Then the stdout should match /Stack \(empty\)/
-    And the stdout should match /Stack \(full\)/
+  Scenario Outline: Nested example groups
+    Given a file named "nested_example_groups.rb" with:
+    """
+    require 'spec/autorun'
 
-  Scenario: Run with spec
-    Given the file ../../examples/passing/stack_spec_with_nested_example_groups.rb
-    When I run it with the spec command -fs
-    Then the stdout should match /Stack \(empty\)/
-    And the stdout should match /Stack \(full\)/
+    describe "Some Object" do
+      describe "with some more context" do
+        it "should do this" do
+          true.should be_true
+        end
+      end
+      describe "with some other context" do
+        it "should do that" do
+          false.should be_false
+        end
+      end
+    end
+    """
+    When I run "<Command> nested_example_groups.rb -fs"
+    Then the stdout should match /Some Object with some more context/
+    And the stdout should match /Some Object with some other context/
+
+  Scenarios: Run with ruby and spec
+    | Command |
+    | ruby    |
+    | spec    |

data/features/extensions/custom_example_group.feature

@@ -0,0 +1,19 @@
+Feature: custom example group
+
+  Scenario: simple custom example group
+    Given a file named "custom_example_group_spec.rb" with:
+    """
+    class CustomGroup < Spec::ExampleGroup
+    end
+
+    Spec::Example::ExampleGroupFactory.default(CustomGroup)
+
+    describe "setting a default example group base class" do
+      it "should use that class by default" do
+        CustomGroup.should === self
+      end
+    end
+    """
+    When I run "spec custom_example_group_spec.rb"
+    Then the stdout should match "1 example, 0 failures"
+

data/features/formatters/custom_formatter.feature

@@ -0,0 +1,30 @@
+Feature: custom formatters
+
+  In order to format output/reporting to my particular needs
+  As an RSpec user
+  I want to create my own custom output formatters
+
+  Scenario: specdoc format
+    Given a file named "custom_formatter.rb" with:
+      """
+      require 'spec/runner/formatter/base_formatter'
+      class CustomFormatter < Spec::Runner::Formatter::BaseFormatter
+        def initialize(options, output)
+          @output = output
+        end
+        def example_started(proxy)
+          @output << "example: " << proxy.description
+        end
+      end
+      """
+    And a file named "simple_example_spec.rb" with:
+    """
+      describe "my group" do
+        specify "my example" do
+        end
+      end
+    """
+
+    When I run "spec simple_example_spec.rb --require custom_formatter.rb --format CustomFormatter"
+    Then the exit code should be 0
+    And the stdout should match "example: my example"

data/features/heckle/heckle.feature

@@ -5,7 +5,7 @@ Feature: heckle a class
   I want to heckle a class
 
   Scenario: Heckle finds problems
-    Given the following spec:
+    Given a file named "heckle_fail_spec.rb" with:
       """
       class Thing
         def a_or_b
@@ -16,19 +16,19 @@ Feature: heckle a class
           end
         end
       end
-      
+
       describe Thing do
         it "returns a for true" do
           Thing.new.a_or_b.should == "a"
         end
       end
       """
-    When I run it with the spec command --heckle Thing
+    When I run "spec heckle_fail_spec.rb --heckle Thing"
     Then the stdout should match "The following mutations didn't cause test failures:"
     But the stdout should not match "FAILED"
-    
+
   Scenario: Heckle does not find a problem
-    Given the following spec:
+    Given a file named "heckle_success_spec.rb" with:
       """
       class Thing
         def a_or_b(key)
@@ -50,7 +50,7 @@ Feature: heckle a class
         end
       end
       """
-    When I run it with the spec command --heckle Thing
+    When I run "spec heckle_success_spec.rb --heckle Thing"
     Then the stdout should match "No mutants survived"
     But the stdout should not match "FAILED"
-    
+

data/features/interop/examples_and_tests_together.feature

@@ -4,23 +4,67 @@ Feature: Spec and test together
   I want to run a few specs alongside my existing Test::Unit tests
   So that I can experience a smooth, gradual migration path
 
-  Scenario: Run with ruby
-    Given the file ../../resources/test/spec_and_test_together.rb
+  Scenario Outline: Run specs and tests together
+    Given a file named "spec_and_test_together.rb" with:
+    """
+    require 'spec/autorun'
+    require 'spec/test/unit'
 
-    When I run it with the ruby interpreter -fs
+    describe "An Example" do
+      it "should pass with assert" do
+        assert true
+      end
 
-    Then the exit code should be 256
-    And the stdout should match "ATest"
-    And the stdout should match "Test::Unit::AssertionFailedError in 'An Example should fail with assert'"
-    And the stdout should match "'An Example should fail with should' FAILED"
-    And the stdout should match "10 examples, 6 failures"
-    And the stdout should match /expected: 40,\s*got: 4/m
-    And the stdout should match /expected: 50,\s*got: 5/m
-    
-  Scenario: Run with spec
-    Given the file ../../resources/test/spec_and_test_together.rb
+      it "should fail with assert" do
+        assert false
+      end
+
+      it "should pass with should" do
+        1.should == 1
+      end
+
+      it "should fail with should" do
+        1.should == 2
+      end
+    end
 
-    When I run it with the spec command -fs
+    class ATest < Test::Unit::TestCase
+      def test_should_pass_with_assert
+        assert true
+      end
+
+      def test_should_fail_with_assert
+        assert false
+      end
+
+      def test_should_pass_with_should
+        1.should == 1
+      end
+
+      def test_should_fail_with_should
+        1.should == 2
+      end
+
+      def setup
+        @from_setup ||= 3
+        @from_setup += 1
+      end
+
+      def test_should_fail_with_setup_method_variable
+        @from_setup.should == 40
+      end
+
+      before do
+        @from_before = @from_setup + 1
+      end
+
+      def test_should_fail_with_before_block_variable
+        @from_before.should == 50
+      end
+    end
+    """
+
+    When I run "<Command> spec_and_test_together.rb -fs"
 
     Then the exit code should be 256
     And the stdout should match "ATest"
@@ -29,3 +73,8 @@ Feature: Spec and test together
     And the stdout should match "10 examples, 6 failures"
     And the stdout should match /expected: 40,\s*got: 4/m
     And the stdout should match /expected: 50,\s*got: 5/m
+
+  Scenarios: run with ruby and spec
+    | Command |
+    | ruby    |
+    | spec    |

data/features/interop/rspec_output.feature

@@ -0,0 +1,25 @@
+Feature: spec output
+
+  When running in interop mode with test/unit, RSpec will output
+  the RSpec summary, but not the test/unit summary.
+
+  Scenario Outline: Interop mode with test/unit
+    Given a file named "simple_spec.rb" with:
+    """
+    require 'spec/autorun'
+
+    describe "Running an Example" do
+      it "should not output twice" do
+        true.should be_true
+      end
+    end
+    """
+    When I run "<Command> simple_spec.rb"
+    Then the exit code should be 0
+    And the stdout should not match /\d+ tests, \d+ assertions, \d+ failures, \d+ errors/m
+    And the stdout should match "1 example, 0 failures"
+
+  Scenarios: Run with ruby and CommandLine object
+    | Command     |
+    | ruby        |
+    | cmdline.rb  |

data/features/interop/test_but_not_test_unit.feature

@@ -3,12 +3,24 @@ Story: Test is defined, but not Test::Unit
   As an RSpec user who has my own library named Test (but not Test::Unit)
   I want to run examples without getting Test::Unit NameErrors
 
-  Scenario: Run with ruby
-    Given the file ../../resources/test/spec_including_test_but_not_unit.rb
-    When I run it with the ruby interpreter
-    Then the stderr should not match "Test::Unit"
+  Scenario Outline: Spec including Test const but not Test::Unit
+    Given a file named "spec_including_test_but_not_unit.rb" with:
+    """
+    require 'spec/autorun'
+
+    module Test
+    end
 
-  Scenario: Run with spec
-    Given the file ../../resources/test/spec_including_test_but_not_unit.rb
-    When I run it with the spec command
+    describe "description" do
+      it "should description" do
+        1.should == 1
+      end
+    end
+    """
+    When I run "<Command> spec_including_test_but_not_unit.rb"
     Then the stderr should not match "Test::Unit"
+
+  Scenarios: Run with ruby and spec
+    | Command |
+    | ruby    |
+    | spec    |

data/features/interop/test_case_with_should_methods.feature

@@ -4,14 +4,43 @@ Story: Test::Unit::TestCase extended by rspec with should methods
   I want to use should_* methods in a Test::Unit::TestCase
   So that I use RSpec with classes and methods that look more like RSpec examples
 
-  Scenario: Run with ruby
-    Given the file ../../resources/test/test_case_with_should_methods.rb
-    When I run it with the ruby interpreter
-    Then the exit code should be 256
-    And the stdout should match "5 examples, 3 failures"
+  Scenario Outline: TestCase with should methods
+    Given a file named "test_case_with_should_methods.rb" with:
+    """
+    require 'spec/autorun'
+    require 'spec/test/unit'
+
+    class MyTest < Test::Unit::TestCase
+      def should_pass_with_should
+        1.should == 1
+      end
+
+      def should_fail_with_should
+        1.should == 2
+      end
 
-  Scenario: Run with spec
-    Given the file ../../resources/test/test_case_with_should_methods.rb
-    When I run it with the spec command
+      def should_pass_with_assert
+        assert true
+      end
+
+      def should_fail_with_assert
+        assert false
+      end
+
+      def test
+        raise "This is not a real test"
+      end
+
+      def test_ify
+        raise "This is a real test"
+      end
+    end
+    """
+    When I run "<Command> test_case_with_should_methods.rb"
     Then the exit code should be 256
     And the stdout should match "5 examples, 3 failures"
+
+  Scenarios: Run with ruby and spec
+    | Command |
+    | ruby    |
+    | spec    |

data/features/matchers/{create_matcher.feature → define_matcher.feature}

@@ -1,13 +1,13 @@
-Feature: custom matcher shortcut
+Feature: define matcher
 
   In order to express my domain clearly in my code examples
   As an RSpec user
-  I want a shortcut for create custom matchers
+  I want a shortcut to define custom matchers
 
-  Scenario: creating a matcher with default messages
-    Given the following spec:
+  Scenario: define a matcher with default messages
+    Given a file named "matcher_with_default_message_spec.rb" with:
       """
-      Spec::Matchers.create :be_a_multiple_of do |expected|
+      Spec::Matchers.define :be_a_multiple_of do |expected|
         match do |actual|
           actual % expected == 0
         end
@@ -32,7 +32,7 @@ Feature: custom matcher shortcut
       end
 
       """
-    When I run it with the spec command --format specdoc
+    When I run "spec matcher_with_default_message_spec.rb --format specdoc"
     Then the exit code should be 256
 
     And the stdout should match "should be a multiple of 3"
@@ -43,11 +43,11 @@ Feature: custom matcher shortcut
     And the stdout should match "4 examples, 2 failures"
     And the stdout should match "expected 9 to be a multiple of 4"
     And the stdout should match "expected 9 not to be a multiple of 3"
-    
+
   Scenario: overriding the failure_message_for_should
-    Given the following spec:
+    Given a file named "matcher_with_failure_message_spec.rb" with:
       """
-      Spec::Matchers.create :be_a_multiple_of do |expected|
+      Spec::Matchers.define :be_a_multiple_of do |expected|
         match do |actual|
           actual % expected == 0
         end
@@ -55,21 +55,21 @@ Feature: custom matcher shortcut
           "expected that #{actual} would be a multiple of #{expected}"
         end
       end
-  
+
       # fail intentionally to generate expected output
       describe 9 do
         it {should be_a_multiple_of(4)}
       end
       """
-    When I run it with the spec command
+    When I run "spec matcher_with_failure_message_spec.rb"
     Then the exit code should be 256
     And the stdout should match "1 example, 1 failure"
     And the stdout should match "expected that 9 would be a multiple of 4"
-  
+
   Scenario: overriding the failure_message_for_should_not
-    Given the following spec:
+    Given a file named "matcher_with_failure_for_message_spec.rb" with:
       """
-      Spec::Matchers.create :be_a_multiple_of do |expected|
+      Spec::Matchers.define :be_a_multiple_of do |expected|
         match do |actual|
           actual % expected == 0
         end
@@ -77,21 +77,21 @@ Feature: custom matcher shortcut
           "expected that #{actual} would not be a multiple of #{expected}"
         end
       end
-  
+
       # fail intentionally to generate expected output
       describe 9 do
         it {should_not be_a_multiple_of(3)}
       end
       """
-    When I run it with the spec command
+    When I run "spec matcher_with_failure_for_message_spec.rb"
     Then the exit code should be 256
     And the stdout should match "1 example, 1 failure"
     And the stdout should match "expected that 9 would not be a multiple of 3"
-  
+
   Scenario: overriding the description
-    Given the following spec:
+    Given a file named "matcher_overriding_description_spec.rb" with:
       """
-      Spec::Matchers.create :be_a_multiple_of do |expected|
+      Spec::Matchers.define :be_a_multiple_of do |expected|
         match do |actual|
           actual % expected == 0
         end
@@ -99,30 +99,30 @@ Feature: custom matcher shortcut
           "be multiple of #{expected}"
         end
       end
-  
+
       describe 9 do
         it {should be_a_multiple_of(3)}
       end
-  
+
       describe 9 do
         it {should_not be_a_multiple_of(4)}
       end
       """
-    When I run it with the spec command --format specdoc
+    When I run "spec matcher_overriding_description_spec.rb --format specdoc"
     Then the exit code should be 0
     And the stdout should match "2 examples, 0 failures"
     And the stdout should match "should be multiple of 3"
     And the stdout should match "should not be multiple of 4"
 
   Scenario: with no args
-    Given the following spec:
+    Given a file named "matcher_with_no_args_spec.rb" with:
       """
-      Spec::Matchers.create :have_7_fingers do
+      Spec::Matchers.define :have_7_fingers do
         match do |thing|
           thing.fingers.length == 7
         end
       end
-      
+
       class Thing
         def fingers; (1..7).collect {"finger"}; end
       end
@@ -131,15 +131,15 @@ Feature: custom matcher shortcut
         it {should have_7_fingers}
       end
       """
-    When I run it with the spec command --format specdoc
+    When I run "spec matcher_with_no_args_spec.rb --format specdoc"
     Then the exit code should be 0
     And the stdout should match "1 example, 0 failures"
     And the stdout should match "should have 7 fingers"
-  
+
   Scenario: with multiple args
-    Given the following spec:
+    Given a file named "matcher_with_multiple_args_spec.rb" with:
       """
-      Spec::Matchers.create :be_the_sum_of do |a,b,c,d|
+      Spec::Matchers.define :be_the_sum_of do |a,b,c,d|
         match do |sum|
           a + b + c + d == sum
         end
@@ -149,7 +149,31 @@ Feature: custom matcher shortcut
         it {should be_the_sum_of(1,2,3,4)}
       end
       """
-    When I run it with the spec command --format specdoc
+    When I run "spec matcher_with_multiple_args_spec.rb --format specdoc"
     Then the exit code should be 0
     And the stdout should match "1 example, 0 failures"
     And the stdout should match "should be the sum of 1, 2, 3, and 4"
+    
+  Scenario: with helper methods
+    Given a file named "matcher_with_internal_helper_spec.rb" with:
+      """
+      Spec::Matchers.define :have_same_elements_as do |sample|
+        match do |actual|
+          similar?(sample, actual)
+        end
+        
+        def similar?(a, b)
+          a.sort == b.sort
+        end
+      end
+      
+      describe "these two arrays" do
+        specify "should be similar" do
+          [1,2,3].should have_same_elements_as([2,3,1])
+        end
+      end
+      """
+    When I run "spec matcher_with_internal_helper_spec.rb"
+    Then the exit code should be 0
+    And the stdout should match "1 example, 0 failures"
+