rspec-steps 0.0.8 → 0.0.9

data/doc/README

@@ -2,11 +2,11 @@
 ## ( or: why would I want to relearn how to write specs? )
 
 RSpec Steps allows you to chain examples into a series of steps that run
-in sequence and which stop when a step fails.  It's often incredibly 
-useful to be able to aseemble a series of tests that should all pass, 
+in sequence and which stop when a step fails.  It's often incredibly
+useful to be able to aseemble a series of tests that should all pass,
 but where completely isolating them is less than sensible.
 
-One excellent example is web site integration tests.  With RSpec steps you can 
+One excellent example is web site integration tests.  With RSpec steps you can
 do:
 
          steps "Login and change password" do
@@ -14,42 +14,42 @@ do:
              visit root
              page.should have_text "Login"
            end
-        
+
            it "should successfully log in" do
              fill_in :name, "Johnny User"
              click "Login"
              page.should have_text "Welcome, Johnny!"
            end
-           
-           it "should load the password change form" do 
+
+           it "should load the password change form" do
              click "My Settings"
              click "Update Password"
              page.should have_selector("form#update_password")
-           end     
-        
+           end
+
            it "should change the user's password successfully" do
              fill_in :password, "foobar"
              fill_in :password_confirmation, "foobar"
              click "Change Password"
              page.should have_text "Password changed successfully!"
-             User.find_by_name("Johnny User").valid_password?("foobar").should be_true 
+             User.find_by_name("Johnny User").valid_password?("foobar").should be_true
            end
-        
+
          end
 
 The examples above will be run in order.  State is preserved between examples
-inside a "steps" block: any DB transactions will not roll back until the entire 
-sequence has been complete. 
+inside a "steps" block: any DB transactions will not roll back until the entire
+sequence has been complete.
 
-If any example inside the "steps" block fails, all remaining steps will be marked 
-pending and therefore skipped. 
+If any example inside the "steps" block fails, all remaining steps will be marked
+pending and therefore skipped.
 
 ## Rationale
 
 RSpec's philosophy is that all examples should be completely independent.  This
-is a great philosophy for most purposes, and we recommend you stick to it in 
-almost all cases.  BUT, that complete separation of examples really sucks when 
-you're trying to write long stories involving many requests.   You are usually 
+is a great philosophy for most purposes, and we recommend you stick to it in
+almost all cases.  BUT, that complete separation of examples really sucks when
+you're trying to write long stories involving many requests.   You are usually
 stuck with three choices:
 
 1. Write a sequence of examples, each of which repeats the behavior of all previous examples. Downside: horrendously inefficient.
@@ -62,13 +62,13 @@ and skip subsequent steps after a failure.
 
 ## Caveats and cautions
 
-Don't call "describe" inside of "steps".  The behavior is undefined and probably bad.  It's 
-hard to imagine what this should actually mean in any case.  Future versions of rspec-steps 
+Don't call "describe" inside of "steps".  The behavior is undefined and probably bad.  It's
+hard to imagine what this should actually mean in any case.  Future versions of rspec-steps
 will consider this an error.
 
 Any call to "before" inside a steps block is treated like before(:all) and is run only
-once before the first step.  Or perhaps more accurately, any call to before() is treated 
-like before(:each) ... but for these purposes the entire steps block is treated like a 
+once before the first step.  Or perhaps more accurately, any call to before() is treated
+like before(:each) ... but for these purposes the entire steps block is treated like a
 single example.
 
 ## Advanced stuff:  shared steps
@@ -89,8 +89,8 @@ diverge, you can DRY your code out with shared_steps blocks, like so:
        end
 
        steps "updating password" do
-         perform_steps "For a logged-in user" 
-          
+         perform_steps "For a logged-in user"
+
          it "should update the password" do
            ...
          end
@@ -98,17 +98,24 @@ diverge, you can DRY your code out with shared_steps blocks, like so:
 
        steps "uploading a profile picture" do
          perform_steps "For a logged-in user"
-       
+
          it "should upload a picture" do
             ...
          end
        end
 
+## Versions and Dependencies
+
+0.0.8: Released Jan 11, 2012.
+        NOTES: Will not work with rspec > 2.9.
+
+CURRENT UNRELEASED Jan 31 2013:
+        Specs pass with rspec-core 2.6.0, 2.7.0, 2.8.0, 2.9.0, 2.10.1
+        Specs fail with rspec-core 2.11.x
+
+
 
-       
 
- 
-        
 
 
 

data/lib/rspec-steps/stepwise.rb

@@ -49,7 +49,12 @@ module RSpecStepwise
 
     def stepped_before_hooks(example_group_instance)
       example_group_instance.example = whole_list_example
-      world.run_hook_filtered(:before, :each, self, example_group_instance, whole_list_example)
+
+      if world.respond_to?(:run_hook_filtered) # Rspec < 2.10
+        world.run_hook_filtered(:before, :each, self, example_group_instance, whole_list_example)
+      else # Rspec >= 2.10
+        run_hook(:before, :each, whole_list_example)
+      end
       ancestors.reverse.each { |ancestor| ancestor.run_hook(:before, :each, example_group_instance) }
       store_before_all_ivars(example_group_instance)
     end
@@ -79,7 +84,11 @@ module RSpecStepwise
     def stepped_after_hooks(example_group_instance)
       example_group_instance.example = whole_list_example
       ancestors.each { |ancestor| ancestor.run_hook(:after, :each, example_group_instance) }
-      world.run_hook_filtered(:after, :each, self, example_group_instance, whole_list_example)
+      if world.respond_to?(:run_hook_filtered) # Rspec < 2.10
+        world.run_hook_filtered(:before, :each, self, example_group_instance, whole_list_example)
+      else # Rspec >= 2.10
+        run_hook(:before, :each, whole_list_example)
+      end
     end
 
     def whole_list_example
@@ -89,7 +98,12 @@ module RSpecStepwise
     end
 
     def with_around_hooks(instance, &block)
-      hooks = around_hooks_for(self)
+      if self.respond_to?(:around_hooks_for) # rSpec < 2.10.0
+        hooks = around_hooks_for(self)
+      else
+        hooks = around_each_hooks_for(self) # rSpec >= 2.10.0
+      end
+
       if hooks.empty?
         yield
       else

metadata

@@ -1,104 +1,52 @@
---- !ruby/object:Gem::Specification 
+--- !ruby/object:Gem::Specification
 name: rspec-steps
-version: !ruby/object:Gem::Version 
+version: !ruby/object:Gem::Version
+  version: 0.0.9
   prerelease: 
-  version: 0.0.8
 platform: ruby
-authors: 
+authors:
 - Judson Lester
 - Evan Dorn
 autorequire: 
 bindir: bin
 cert_chain: []
-
-date: 2012-01-11 00:00:00 Z
-dependencies: 
-- !ruby/object:Gem::Dependency 
-  name: rake-rubygems
-  prerelease: false
-  requirement: &id001 !ruby/object:Gem::Requirement 
-    none: false
-    requirements: 
-    - - ">="
-      - !ruby/object:Gem::Version 
-        version: 0.2.0
-  type: :development
-  version_requirements: *id001
-- !ruby/object:Gem::Dependency 
-  name: hanna
-  prerelease: false
-  requirement: &id002 !ruby/object:Gem::Requirement 
-    none: false
-    requirements: 
-    - - ~>
-      - !ruby/object:Gem::Version 
-        version: 0.1.0
-  type: :development
-  version_requirements: *id002
-- !ruby/object:Gem::Dependency 
-  name: mailfactory
-  prerelease: false
-  requirement: &id003 !ruby/object:Gem::Requirement 
-    none: false
-    requirements: 
-    - - ~>
-      - !ruby/object:Gem::Version 
-        version: 1.4.0
-  type: :development
-  version_requirements: *id003
-- !ruby/object:Gem::Dependency 
-  name: rspec
-  prerelease: false
-  requirement: &id004 !ruby/object:Gem::Requirement 
-    none: false
-    requirements: 
-    - - ">="
-      - !ruby/object:Gem::Version 
-        version: "2.0"
-  type: :development
-  version_requirements: *id004
-- !ruby/object:Gem::Dependency 
-  name: bundler
-  prerelease: false
-  requirement: &id005 !ruby/object:Gem::Requirement 
+date: 2013-02-22 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: corundum
+  requirement: &90293470 !ruby/object:Gem::Requirement
     none: false
-    requirements: 
-    - - ~>
-      - !ruby/object:Gem::Version 
-        version: 1.0.0
+    requirements:
+    - - ! '>='
+      - !ruby/object:Gem::Version
+        version: 0.0.25
   type: :development
-  version_requirements: *id005
-- !ruby/object:Gem::Dependency 
-  name: rcov
   prerelease: false
-  requirement: &id006 !ruby/object:Gem::Requirement 
-    none: false
-    requirements: 
-    - - ">="
-      - !ruby/object:Gem::Version 
-        version: "0"
-  type: :development
-  version_requirements: *id006
-- !ruby/object:Gem::Dependency 
+  version_requirements: *90293470
+- !ruby/object:Gem::Dependency
   name: rspec
-  prerelease: false
-  requirement: &id007 !ruby/object:Gem::Requirement 
+  requirement: &90291650 !ruby/object:Gem::Requirement
     none: false
-    requirements: 
-    - - ">="
-      - !ruby/object:Gem::Version 
-        version: "2.6"
+    requirements:
+    - - ! '>='
+      - !ruby/object:Gem::Version
+        version: '2.6'
+        segments:
+        - 2
+        - 6
   type: :runtime
-  version_requirements: *id007
-description: "  I don't like Cucumber.  I don't need plain text stories.  My clients either\n  read code or don't read any test documents, so Cucumber is mostly useless.\n  But often, especially in full integration tests, it would be nice to have\n  steps in a test.\n"
-email: 
+  prerelease: false
+  version_requirements: *90291650
+description: ! "  I don't like Cucumber.  I don't need plain text stories.  My clients
+  either\n  read code or don't read any test documents, so Cucumber is mostly useless.\n
+  \ But often, especially in full integration tests, it would be nice to have\n  steps
+  in a test.\n"
+email:
 - judson@lrdesign.com
 - evan@lrdesign.com
 executables: []
-
 extensions: []
-
-extra_rdoc_files: 
+extra_rdoc_files:
 - doc/README
 - doc/Specifications
 - doc/coverage/rcov-ruby-1_8-gems-rspec-expectations-2_5_0-lib-rspec-matchers-include_rb.html
@@ -217,14 +165,14 @@ extra_rdoc_files:
 - doc/coverage/print.css
 - doc/coverage/rcov-ruby-1_8-gems-rspec-expectations-2_5_0-lib-rspec-matchers-satisfy_rb.html
 - doc/coverage/lib-rspec-steps-duckpunch-object-extensions_rb.html
-files: 
+files:
 - lib/rspec-steps.rb
 - lib/rspec-steps/stepwise.rb
 - lib/rspec-steps/duckpunch/example-group.rb
 - lib/rspec-steps/duckpunch/object-extensions.rb
 - doc/README
 - doc/Specifications
-- spec/example_group.rb
+- spec/example_group_spec.rb
 - spec_help/spec_helper.rb
 - spec_help/gem_test_suite.rb
 - spec_help/rspec-sandbox.rb
@@ -347,35 +295,38 @@ files:
 - doc/coverage/rcov-ruby-1_8-gems-rspec-expectations-2_5_0-lib-rspec-matchers-satisfy_rb.html
 - doc/coverage/lib-rspec-steps-duckpunch-object-extensions_rb.html
 homepage: https://github.com/LRDesign/rspec-steps
-licenses: 
+licenses:
 - MIT
-post_install_message: Another tidy package brought to you by Judson Lester of Logical Reality Design
-rdoc_options: 
+post_install_message: Another tidy package brought to you by Judson Lester of Logical
+  Reality Design
+rdoc_options:
 - --inline-source
 - --main
 - doc/README
 - --title
-- rspec-steps-0.0.8 RDoc
-require_paths: 
+- rspec-steps-0.0.9 RDoc
+require_paths:
 - lib/
-required_ruby_version: !ruby/object:Gem::Requirement 
+required_ruby_version: !ruby/object:Gem::Requirement
   none: false
-  requirements: 
-  - - ">="
-    - !ruby/object:Gem::Version 
-      version: "0"
-required_rubygems_version: !ruby/object:Gem::Requirement 
+  requirements:
+  - - ! '>='
+    - !ruby/object:Gem::Version
+      version: '0'
+      segments:
+      - 0
+      hash: 472080701
+required_rubygems_version: !ruby/object:Gem::Requirement
   none: false
-  requirements: 
-  - - ">="
-    - !ruby/object:Gem::Version 
-      version: "0"
+  requirements:
+  - - ! '>='
+    - !ruby/object:Gem::Version
+      version: '0'
 requirements: []
-
 rubyforge_project: rspec-steps
-rubygems_version: 1.8.11
+rubygems_version: 1.8.15
 signing_key: 
 specification_version: 3
 summary: I want steps in RSpec
-test_files: 
+test_files:
 - spec_help/gem_test_suite.rb