rutabaga 0.0.1 → 0.0.2

data/.travis.yml

@@ -4,6 +4,6 @@ rvm:
   - 1.9.3
   # Gherkin currently failing to build in ruby-head
   # - ruby-head
-  - rbx-19mode
+  # - rbx-19mode
 
 script: bundle exec rspec spec

data/README.md

@@ -2,7 +2,7 @@
 
 Turnip hacks to enable running turnips from inside spec files, rather than outside.
 
-Rutabaga allows you to invert the control of feature files, so that features are called from your `_spec.rb` files rather than the other way around. Step definitions are then put into the `_spec.rb` files as well.
+Rutabaga allows you to invert the control of feature files, so that features are called from your `_spec.rb` files rather than the other way around. Step definitions are then put into the `_spec.rb` files as well. The steps are then scoped to that particular test.
 
 This means that it is simple to create tests that are described by a class (such as controller tests in rspec-rails).
 
@@ -16,14 +16,14 @@ gem install rutabaga
 
 Or add it to your Gemfile and run `bundle`.
 
-``` ruby
+```ruby
 group :test do
-  gem "rutabaga", :git => 'git://github.com/simplybusiness/rutabaga.git'
+  gem "rutabaga"
 end
 ```
 
 Now edit the `.rspec` file in your project directory (create it if doesn't
-exist), and add the following line:
+exist), and add the following:
 
 ```
 -r rutabaga
@@ -31,14 +31,14 @@ exist), and add the following line:
 
 Add the follwing lines to the bottom of your `spec_helper.rb` (assuming you want to use Capybara and the final one if you wish to have step definitions outside of your spec files:
 
-```
+```ruby
 require 'turnip/capybara'
 Dir.glob("spec/features/step_definitions/**/*_steps.rb") { |f| load f, true }
 ```
 
 In order to get `rake` or `bundle exec rake` to work properly, you might need to add this in the file `lib/tasks/rspec.rake` (at least for rails)
 
-```
+```ruby
 if defined? RSpec # otherwise fails on non-live environments
   desc "Run all specs/features in spec directory"
   RSpec::Core::RakeTask.new(:spec => 'db:test:prepare') do |t|
@@ -55,7 +55,7 @@ Please look in `spec/controllers/feature_test_spec.rb` and `spec/controllers/fea
 
 For file `spec/controllers/test_feature_spec.rb`
 
-```
+```ruby
 it "should run feature" do
   feature
 end
@@ -63,7 +63,7 @@ end
 
 Will run `spec/controllers/test_feature.feature`.
 
-Features are found either with the same name as the spec file, or as specified in the example name `it "/path/to/feature/file.feature"`. So, if you have:
+Features are found either with the same name as the spec file, or as specified in the example name `it "relative_from_root/path/to/feature/file.feature"`. So, if you have:
 
 `spec/controllers/feature_test_spec.rb`
 
@@ -73,7 +73,7 @@ Then the feature will be:
 
 Alternatively, if the feature is specified in the `it`, that takes precedence:
 
-```
+```ruby
 it "spec/features/test.feature" do
     feature
 end
@@ -85,19 +85,23 @@ Will run `spec/features/test.feature`.
 
 Other than these differences, Rutabaga is a tiny shim over Turnip and all features will work as expected.
 
-* Turnip looks anywhere below the `spec` directory for `.feature` files. Rutabaga will only load `.feature` files from below the `spec/features` directory in the old way. This is to avoid conflicts with `.feature` files that are loaded from `_spec.rb` files.
+* Turnip looks anywhere below the `spec` directory for `.feature` files. Rutabaga will only load `.feature` files from below the `spec/features` directory in the old way. This avoids conflicts with `.feature` files that are loaded from `_spec.rb` files.
 
 ## Why?
 
-The fundamental purpose of Turnip/Cucumber is to document the system in end-user readable form.
+* Document business rules in Gherkin/Turnip/Cucumber human readable language
+* Test those rules whereever/however appropriate (not just through Capybara/black box)
+* Use the full power of RSpec (so being able to describe a class and then test it)
+
+From my point of view, the fundamental purpose of Turnip/Cucumber is to document the system in end-user readable form. It is not just to do integration tests.
 
-The most important functionality in a system is the business rules. These range from what appears on a page, to complex rules around when emails should be sent to who. For example, we've written Gherkin tests for what amount to charge a customer when they change what's covered on their insurance policy.
+The most important functionality in a system is the business rules. These range from what appears on a page, to complex rules around when emails should be sent to who. For example, we've written Gherkin tests to test premium changes when a customer changes their insurance coverage.
 
-Those rules are often implemented in a Model, a lib class, or some other specific class in the system, especially if the application is well modularized.
+These rules are often implemented in a Model, a lib class, or some other specific class in the system, especially if the application is well modularized.
 
 In any case, business rules are usually implemented somewhere inside a class tested by a unit test. I want to get those business rules tested in Cucumber/Turnip without having to go through the whole system, and without having to have duplicate tests, one inside my rspec and another inside my features.
 
-My goal is to test just the business rule, in Turnip, and not the login, the html, the steps to get there, etc. That way, when the rule changes, I change the Turnip, the test code and the class in question. My test is not affected by wider ranging changes, and therefore less brittle. (This should all be familiar territory.) I guess, in that sense, the code runs at the unit code level, but is an acceptance test.
+My goal is to test just the business rule, in Turnip, and not the login, the html, the steps to get there, etc. That way, when the rule changes, I change the Turnip, the test code and the class in question. My test is not affected by wider ranging changes, and therefore less brittle. I guess, in that sense, the code runs at the unit code level, but is an acceptance test.
 
 ## Contributing
 
@@ -109,4 +113,4 @@ My goal is to test just the business rule, in Turnip, and not the login, the htm
 
 ## Copyright
 
-Copyright © 2012 SimplyBusiness. See LICENSE for details.
+Copyright © 2012 Simply Business. See LICENSE for details.

data/lib/rutabaga.rb

@@ -1,3 +1,4 @@
+require 'rutabaga/rspec_scary_speed_fix'
 require 'rutabaga/version'
 require 'turnip'
 require 'rutabaga/feature'

data/lib/rutabaga/rspec_scary_speed_fix.rb

@@ -0,0 +1,11 @@
+# speed up rspec under ruby 1.9 because it doesn't work otherwise
+if RUBY_VERSION > '1.9.2'
+  class Object
+    def to_ary ; nil ; end
+    def to_hash ; nil ; end
+  end
+
+  class String
+    def to_path ; self ; end
+  end
+end

data/lib/rutabaga/version.rb

@@ -1,3 +1,3 @@
 module Rutabaga
-  VERSION = '0.0.1'
+  VERSION = '0.0.2'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: rutabaga
 version: !ruby/object:Gem::Version
-  version: 0.0.1
+  version: 0.0.2
   prerelease: 
 platform: ruby
 authors:
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2012-08-22 00:00:00.000000000 Z
+date: 2012-08-24 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: turnip
@@ -47,6 +47,7 @@ files:
 - lib/.DS_Store
 - lib/rutabaga.rb
 - lib/rutabaga/feature.rb
+- lib/rutabaga/rspec_scary_speed_fix.rb
 - lib/rutabaga/version.rb
 - rutabaga.gemspec
 - spec/feature_spec.rb