rspec 1.3.2 → 2.0.0.a2

data/features/expectations/expect_change.feature

@@ -1,65 +0,0 @@
-Feature: expect change
-
-  Expect some code (wrapped in a proc) to change the state of some object.
-  
-  Scenario: expecting change
-    Given a file named "expect_change.rb" with:
-      """
-      class Counter
-        class << self
-          def increment
-            @count ||= 0
-            @count += 1
-          end
-          
-          def count
-            @count ||= 0
-          end
-        end
-      end
-      
-      describe Counter, "#increment" do
-        it "should increment the count" do
-          expect{Counter.increment}.to change{Counter.count}.from(0).to(1)
-        end
-
-        # deliberate failure
-        it "should increment the count by 2" do
-          expect{Counter.increment}.to change{Counter.count}.by(2)
-        end
-      end
-      """
-    When I run "spec expect_change.rb"
-    Then the stdout should include "2 examples, 1 failure"
-    Then the stdout should include "should have been changed by 2, but was changed by 1"
-
-  Scenario: expecting no change
-    Given a file named "expect_no_change.rb" with:
-      """
-      class Counter
-        class << self
-          def increment
-            @count ||= 0
-            @count += 1
-          end
-          
-          def count
-            @count ||= 0
-          end
-        end
-      end
-
-      describe Counter, "#increment" do
-        it "should not increment the count by 2" do
-          expect{Counter.increment}.to_not change{Counter.count}.from(0).to(2)
-        end
-
-        # deliberate failure
-        it "should not increment the count by 1" do
-          expect{Counter.increment}.to_not change{Counter.count}.by(1)
-        end
-      end
-      """
-    When I run "spec expect_no_change.rb"
-    Then the stdout should include "2 examples, 1 failure"
-    Then the stdout should include "should not have changed, but did change from 1 to 2"

data/features/expectations/expect_error.feature

@@ -1,44 +0,0 @@
-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 include "2 examples, 1 failure"
-    Then the stdout should include "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 include "2 examples, 1 failure"
-    Then the stdout should include "undefined method `non_existent_message'"
-

data/features/extensions/custom_example_group.feature

@@ -1,19 +0,0 @@
-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 "a custom group set as the default" do
-        it "becomes the default base class for example groups" do
-          CustomGroup.should === self
-        end
-      end
-      """
-    When I run "spec custom_example_group_spec.rb"
-    Then the stdout should include "1 example, 0 failures"
-

data/features/formatters/custom_formatter.feature

@@ -1,30 +0,0 @@
-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 include "example: my example"

data/features/formatters/nested_formatter.feature

@@ -1,32 +0,0 @@
-Feature: nested formatter
-
-  The nested formatter follows the nesting in each spec.
-
-  Scenario: parallel contexts
-    Given a file named "simple_example_spec.rb" with:
-      """
-      describe "first group" do
-        context "with context" do
-          specify "does something" do
-          end
-        end
-      end
-      describe "second group" do
-        context "with context" do
-          specify "does something" do
-          end
-        end
-      end
-      """
-
-    When I run "spec simple_example_spec.rb --format nested"
-    Then the exit code should be 0
-    And the stdout should include
-      """
-      first group
-        with context
-          does something
-      second group
-        with context
-          does something
-      """

data/features/interop/cucumber_stubs_dont_leak.feature

@@ -1,11 +0,0 @@
-Feature: Cucumber Stubs Don't Leak
-  In order to not explode from frustration
-  a developer
-  does not want rspec stubs to leak between cucumber scenarios
-
-  Scenario: Create a stub
-    When I stub "nap" on "Time" to "When I Get Cranky"
-    Then calling "nap" on "Time" should return "When I Get Cranky"
-
-  Scenario: Check to see if the stub leaked
-    Then "nap" should not be defined on "Time"

data/features/interop/examples_and_tests_together.feature

@@ -1,84 +0,0 @@
-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 'spec/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
-      
-      define_method :"test: should run with strange name" do
-        assert true
-      end
-    end
-    """
-
-    When I run "<Command> spec_and_test_together.rb -fs"
-
-    Then the exit code should be 256
-    And the stdout should include "ATest"
-    And the stdout should include "Test::Unit::AssertionFailedError in 'An Example should fail with assert'"
-    And the stdout should include "'An Example should fail with should' FAILED"
-    And the stdout should include "11 examples, 6 failures"
-    And the stdout should include /expected: 40,\s*got: 4/m
-    And the stdout should include /expected: 50,\s*got: 5/m
-
-  Scenarios: run with ruby and spec
-    | Command |
-    | ruby    |
-    | spec    |

data/features/interop/rspec_output.feature

@@ -1,25 +0,0 @@
-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 include "1 example, 0 failures"
-
-  Scenarios: Run with ruby and CommandLine object
-    | Command     |
-    | ruby        |
-    | cmdline.rb  |

data/features/interop/test_but_not_test_unit.feature

@@ -1,26 +0,0 @@
-Feature: 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 'spec/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/interop/test_case_with_should_methods.feature

@@ -1,46 +0,0 @@
-Feature: 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 '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
-
-      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 include "5 examples, 3 failures"
-
-  Scenarios: Run with ruby and spec
-    | Command |
-    | ruby    |
-    | spec    |

data/features/load_paths/add_lib_to_load_path.feature

@@ -1,20 +0,0 @@
-Feature: add ./lib to load path
-  In order to ...
-  As a spec author
-  I want rspec to add ./lib to the load path
-
-  Scenario: spec helper
-    Given a directory named "spec"
-    And a file named "example.rb" with:
-      """
-      describe $LOAD_PATH do
-        it "begins with 'lib' in the current directory in the load path" do
-          libdir = File.expand_path(File.join(File.dirname(__FILE__), 'lib'))
-          $LOAD_PATH.should include(libdir)
-        end
-      end
-      """
-    When I run "spec example.rb"
-    Then the stdout should include "1 example, 0 failures"
-    And  the exit code should be 0
-

data/features/load_paths/add_spec_to_load_path.feature

@@ -1,20 +0,0 @@
-Feature: add 'spec' to load path
-  In order to ...
-  As a spec author
-  I want rspec to add 'spec to the load path
-
-  Scenario: add 'spec' to load path
-    Given a directory named "spec"
-    And a file named "example.rb" with:
-      """
-      describe $LOAD_PATH do
-        it "includes with 'spec' in the current directory in the load path" do
-          specdir = File.expand_path(File.join(File.dirname(__FILE__), 'spec'))
-          $LOAD_PATH.should include(specdir)
-        end
-      end
-      """
-    When I run "spec example.rb"
-    Then the stdout should include "1 example, 0 failures"
-    And  the exit code should be 0
-

data/features/matchers/define_diffable_matcher.feature

@@ -1,26 +0,0 @@
-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:
-      """
-      Spec::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 include "should be just like \"that\""
-    And the stdout should include "Diff:\n@@ -1,2 +1,2 @@\n-that\n+this"