rspec-core 2.0.0.beta.3 → 2.0.0.beta.4

data/specs.watchr

@@ -31,9 +31,11 @@ end
 # --------------------------------------------------
 # Watchr Rules
 # --------------------------------------------------
-watch('^spec/(.*)_spec\.rb'  )   { |m| run_test_matching(m[1]) }
-watch('^lib/(.*)\.rb'               )   { |m| run_test_matching(m[1]) }
-watch('^spec/spec_helper\.rb')   { run_all_tests }
+watch('^spec/(.*)_spec\.rb')   { |m| run_test_matching(m[1]) }
+watch('^lib/(.*)\.rb')         { |m| run_test_matching(m[1]) }
+watch('^spec/spec_helper\.rb') { run_all_tests }
+watch('^spec/support/.*\.rb')   { run_all_tests }
+
 # --------------------------------------------------
 # Signal Handling
 # --------------------------------------------------

metadata

@@ -7,8 +7,8 @@ version: !ruby/object:Gem::Version
   - 0
   - 0
   - beta
-  - 3
-  version: 2.0.0.beta.3
+  - 4
+  version: 2.0.0.beta.4
 platform: ruby
 authors: 
 - Chad Humphries
@@ -17,7 +17,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2010-03-08 00:00:00 -06:00
+date: 2010-03-15 00:00:00 -05:00
 default_executable: 
 dependencies: 
 - !ruby/object:Gem::Dependency 
@@ -32,8 +32,8 @@ dependencies:
         - 0
         - 0
         - beta
-        - 3
-        version: 2.0.0.beta.3
+        - 4
+        version: 2.0.0.beta.4
   type: :development
   version_requirements: *id001
 - !ruby/object:Gem::Dependency 
@@ -48,8 +48,8 @@ dependencies:
         - 0
         - 0
         - beta
-        - 3
-        version: 2.0.0.beta.3
+        - 4
+        version: 2.0.0.beta.4
   type: :development
   version_requirements: *id002
 - !ruby/object:Gem::Dependency 
@@ -66,6 +66,20 @@ dependencies:
         version: 0.5.3
   type: :development
   version_requirements: *id003
+- !ruby/object:Gem::Dependency 
+  name: autotest
+  prerelease: false
+  requirement: &id004 !ruby/object:Gem::Requirement 
+    requirements: 
+    - - ">="
+      - !ruby/object:Gem::Version 
+        segments: 
+        - 4
+        - 2
+        - 9
+        version: 4.2.9
+  type: :development
+  version_requirements: *id004
 description: Rspec runner and example group classes
 email: dchelimsky@gmail.com;chad.humphries@gmail.com
 executables: 
@@ -85,6 +99,7 @@ files:
 - TODO.markdown
 - Upgrade.markdown
 - VERSION
+- autotest/discover.rb
 - bin/rspec
 - bin/spec
 - cucumber.yml
@@ -135,20 +150,13 @@ files:
 - example_specs/passing/yielding_example.rb
 - example_specs/ruby1.9.compatibility/access_to_constants_spec.rb
 - example_specs/spec_helper.rb
-- features-pending/formatters/custom_formatter.feature
-- features-pending/heckle/heckle.feature
-- features-pending/interop/examples_and_tests_together.feature
-- features-pending/interop/rspec_output.feature
-- features-pending/interop/test_but_not_test_unit.feature
-- features-pending/interop/test_case_with_should_methods.feature
-- features-pending/mocks/stub_implementation.feature
-- features-pending/pending/pending_examples.feature
 - features/command_line/example_name_option.feature
 - features/command_line/line_number_appended_to_path.feature
 - features/command_line/line_number_option.feature
 - features/configuration/spec_opts.feature
 - features/example_groups/describe_aliases.feature
 - features/example_groups/nested_groups.feature
+- features/formatters/custom_formatter.feature
 - features/hooks/around_hook.feature
 - features/hooks/before_and_after_hooks.feature
 - features/hooks/described_class.feature
@@ -157,9 +165,11 @@ files:
 - features/mock_framework_integration/use_mocha.feature
 - features/mock_framework_integration/use_rr.feature
 - features/mock_framework_integration/use_rspec.feature
+- features/pending/pending_examples.feature
 - features/subject/explicit_subject.feature
 - features/subject/implicit_subject.feature
 - features/support/env.rb
+- lib/autotest/rspec2.rb
 - lib/rspec/autorun.rb
 - lib/rspec/core.rb
 - lib/rspec/core/around_proxy.rb
@@ -194,6 +204,8 @@ files:
 - lib/rspec/core/world.rb
 - rspec-core.gemspec
 - script/console
+- spec/autotest/failed_results_re_spec.rb
+- spec/autotest/rspec_spec.rb
 - spec/rspec/core/command_line_options_spec.rb
 - spec/rspec/core/configuration_spec.rb
 - spec/rspec/core/example_group_spec.rb
@@ -218,6 +230,7 @@ files:
 - spec/rspec/core_spec.rb
 - spec/ruby_forker.rb
 - spec/spec_helper.rb
+- spec/support/matchers.rb
 - specs.watchr
 has_rdoc: true
 homepage: http://github.com/rspec/core
@@ -226,7 +239,7 @@ licenses: []
 post_install_message: |
   **************************************************
   
-    Thank you for installing rspec-core-2.0.0.beta.3
+    Thank you for installing rspec-core-2.0.0.beta.4
   
     This is beta software. If you are looking
     for a supported production release, please
@@ -260,8 +273,10 @@ rubyforge_project: rspec
 rubygems_version: 1.3.6
 signing_key: 
 specification_version: 3
-summary: rspec-core-2.0.0.beta.3
+summary: rspec-core-2.0.0.beta.4
 test_files: 
+- spec/autotest/failed_results_re_spec.rb
+- spec/autotest/rspec_spec.rb
 - spec/rspec/core/command_line_options_spec.rb
 - spec/rspec/core/configuration_spec.rb
 - spec/rspec/core/example_group_spec.rb
@@ -286,3 +301,4 @@ test_files:
 - spec/rspec/core_spec.rb
 - spec/ruby_forker.rb
 - spec/spec_helper.rb
+- spec/support/matchers.rb

data/features-pending/heckle/heckle.feature

@@ -1,56 +0,0 @@
-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

@@ -1,80 +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 '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

@@ -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 '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

@@ -1,26 +0,0 @@
-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

@@ -1,46 +0,0 @@
-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/mocks/stub_implementation.feature

@@ -1,26 +0,0 @@
-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

@@ -1,81 +0,0 @@
-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"