rspec-core 2.0.0.a1

data/features-pending/expectations/expect_error.feature

@@ -0,0 +1,44 @@
+Feature: expect error
+
+  Expect a proc to change the state of some object.
+  
+  Scenario: expect error
+    Given a file named "expect_error.rb" with:
+      """
+      describe Object, "#non_existent_message" do
+        it "should raise" do
+          expect{Object.non_existent_message}.to raise_error(NameError)
+        end
+      end
+
+      #deliberate failure
+      describe Object, "#public_instance_methods" do
+        it "should raise" do
+          expect{Object.public_instance_methods}.to raise_error(NameError)
+        end
+      end
+      """
+    When I run "spec expect_error.rb"
+    Then the stdout should match "2 examples, 1 failure"
+    Then the stdout should match "expected NameError but nothing was raised"
+
+  Scenario: expect no error
+    Given a file named "expect_no_error.rb" with:
+      """
+      describe Object, "#public_instance_methods" do
+        it "should not raise" do
+          expect{Object.public_instance_methods}.to_not raise_error(NameError)
+        end
+      end
+
+      #deliberate failure
+      describe Object, "#non_existent_message" do
+        it "should not raise" do
+          expect{Object.non_existent_message}.to_not raise_error(NameError)
+        end
+      end
+      """
+    When I run "spec expect_no_error.rb"
+    Then the stdout should match "2 examples, 1 failure"
+    Then the stdout should match "undefined method `non_existent_message'"
+

data/features-pending/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-pending/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-pending/heckle/heckle.feature

@@ -0,0 +1,56 @@
+Feature: heckle a class
+
+  As an RSpec user who wants to verify that
+    my specs cover what I think it covers
+  I want to heckle a class
+
+  Scenario: Heckle finds problems
+    Given a file named "heckle_fail_spec.rb" with:
+      """
+      class Thing
+        def a_or_b
+          if true
+            "a"
+          else
+            "b"
+          end
+        end
+      end
+
+      describe Thing do
+        it "returns a for true" do
+          Thing.new.a_or_b.should == "a"
+        end
+      end
+      """
+    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 a file named "heckle_success_spec.rb" with:
+      """
+      class Thing
+        def a_or_b(key)
+          if key
+            "a"
+          else
+            "b"
+          end
+        end
+      end
+
+      describe Thing do
+        it "returns a for true" do
+          Thing.new.a_or_b(true).should == "a"
+        end
+
+        it "returns b for false" do
+          Thing.new.a_or_b(false).should == "b"
+        end
+      end
+      """
+    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-pending/interop/examples_and_tests_together.feature

@@ -0,0 +1,80 @@
+Feature: Spec and test together
+
+  As an RSpec adopter with existing Test::Unit tests
+  I want to run a few specs alongside my existing Test::Unit tests
+  So that I can experience a smooth, gradual migration path
+
+  Scenario Outline: Run specs and tests together
+    Given a file named "spec_and_test_together.rb" with:
+    """
+    require 'rspec/autorun'
+    require 'spec/test/unit'
+
+    describe "An Example" do
+      it "should pass with assert" do
+        assert true
+      end
+
+      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
+
+    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"
+    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
+
+  Scenarios: run with ruby and spec
+    | Command |
+    | ruby    |
+    | spec    |

data/features-pending/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 'rspec/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 rspec/commands
+    | Command     |
+    | ruby        |
+    | cmdline.rb  |

data/features-pending/interop/test_but_not_test_unit.feature

@@ -0,0 +1,26 @@
+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 Outline: Spec including Test const but not Test::Unit
+    Given a file named "spec_including_test_but_not_unit.rb" with:
+    """
+    require 'rspec/autorun'
+
+    module Test
+    end
+
+    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-pending/interop/test_case_with_should_methods.feature

@@ -0,0 +1,46 @@
+Story: Test::Unit::TestCase extended by rspec with should methods
+
+  As an RSpec adopter with existing Test::Unit tests
+  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 Outline: TestCase with should methods
+    Given a file named "test_case_with_should_methods.rb" with:
+    """
+    require 'rspec/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
+
+      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-pending/matchers/define_diffable_matcher.feature

@@ -0,0 +1,26 @@
+Feature: define diffable matcher
+
+  When a matcher is defined as diffable, and the --diff
+  flag is set, the output will include a diff of the submitted
+  objects.
+
+  Scenario: define a diffable matcher
+    Given a file named "diffable_matcher_spec.rb" with:
+      """
+      Rspec::Matchers.define :be_just_like do |expected|
+        match do |actual|
+          actual == expected
+        end
+        
+        diffable
+      end
+
+      describe "this" do
+        it {should be_just_like("that")}
+      end
+      """
+    When I run "spec diffable_matcher_spec.rb --diff"
+    Then the exit code should be 256
+
+    And the stdout should match "should be just like \"that\""
+    And the stdout should match "Diff:\n@@ -1,2 +1,2 @@\n-that\n+this"

data/features-pending/matchers/define_matcher.feature

@@ -0,0 +1,179 @@
+Feature: define matcher
+
+  In order to express my domain clearly in my code examples
+  As an RSpec user
+  I want a shortcut to define custom matchers
+
+  Scenario: define a matcher with default messages
+    Given a file named "matcher_with_default_message_spec.rb" with:
+      """
+      Rspec::Matchers.define :be_a_multiple_of do |expected|
+        match do |actual|
+          actual % expected == 0
+        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
+
+      # fail intentionally to generate expected output
+      describe 9 do
+        it {should be_a_multiple_of(4)}
+      end
+
+      # fail intentionally to generate expected output
+      describe 9 do
+        it {should_not be_a_multiple_of(3)}
+      end
+
+      """
+    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"
+    And the stdout should match "should not be a multiple of 4"
+    And the stdout should match "should be a multiple of 4 (FAILED - 1)"
+    And the stdout should match "should not be a multiple of 3 (FAILED - 2)"
+
+    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 a file named "matcher_with_failure_message_spec.rb" with:
+      """
+      Rspec::Matchers.define :be_a_multiple_of do |expected|
+        match do |actual|
+          actual % expected == 0
+        end
+        failure_message_for_should do |actual|
+          "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 "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 a file named "matcher_with_failure_for_message_spec.rb" with:
+      """
+      Rspec::Matchers.define :be_a_multiple_of do |expected|
+        match do |actual|
+          actual % expected == 0
+        end
+        failure_message_for_should_not do |actual|
+          "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 "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 a file named "matcher_overriding_description_spec.rb" with:
+      """
+      Rspec::Matchers.define :be_a_multiple_of do |expected|
+        match do |actual|
+          actual % expected == 0
+        end
+        description do
+          "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 "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 a file named "matcher_with_no_args_spec.rb" with:
+      """
+      Rspec::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
+
+      describe Thing do
+        it {should have_7_fingers}
+      end
+      """
+    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 a file named "matcher_with_multiple_args_spec.rb" with:
+      """
+      Rspec::Matchers.define :be_the_sum_of do |a,b,c,d|
+        match do |sum|
+          a + b + c + d == sum
+        end
+      end
+
+      describe 10 do
+        it {should be_the_sum_of(1,2,3,4)}
+      end
+      """
+    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:
+      """
+      Rspec::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"
+