rspec-core 2.0.0.beta.8 → 2.0.0.beta.9

data/README.markdown

@@ -1,14 +1,14 @@
-# Rspec Core
+# RSpec Core
 
-Rspec is an automated testing framework for Ruby, designed for use in Behaviour
-Driven Development and Test Driven Development.
+Behaviour Driven Development for Ruby
 
-rspec-core includes the Rspec runner, output formatters, and the `rspec`
-command.
+## Upgrading from rspec-1.x
+
+See Upgrade.markdown
 
 ## Install
 
-    [sudo] gem install rspec --prerelease
+    gem install rspec --prerelease
 
 This will install the rspec, rspec-core, rspec-expectations and rspec-mocks
 gems.
@@ -16,7 +16,7 @@ gems.
 ## Get Started
 
 Start with a simple example of behavior you expect from your system. Do
-this before you write any code:
+this before you write any implementation code:
 
     # in spec/calculator_spec.rb
     describe Calculator, "add" do
@@ -42,7 +42,7 @@ Implement the simplest solution:
 Be sure to require the implementation file in the spec:
 
     # in spec/calculator_spec.rb
-    # - Rspec adds ./lib to the $LOAD_PATH, so you can
+    # - RSpec adds ./lib to the $LOAD_PATH, so you can
     #   just require "calculator" directly
     require "calculator"
 

data/Rakefile

@@ -13,15 +13,15 @@ begin
   require 'jeweler'
   Jeweler::Tasks.new do |gem|
     gem.name = "rspec-core"
-    gem.version = Rspec::Core::Version::STRING
-    gem.summary = "rspec-core-#{Rspec::Core::Version::STRING}"
-    gem.description = 'Rspec runner and example group classes'
+    gem.version = RSpec::Core::Version::STRING
+    gem.summary = "rspec-core-#{RSpec::Core::Version::STRING}"
+    gem.description = 'RSpec runner and example group classes'
     gem.email = "dchelimsky@gmail.com;chad.humphries@gmail.com"
     gem.homepage = "http://github.com/rspec/core"
     gem.authors = ["Chad Humphries", "David Chelimsky"]
     gem.rubyforge_project = "rspec"
-    gem.add_development_dependency "rspec-expectations", ">= #{Rspec::Core::Version::STRING}"
-    gem.add_development_dependency "rspec-mocks", ">= #{Rspec::Core::Version::STRING}"
+    gem.add_development_dependency "rspec-expectations", ">= #{RSpec::Core::Version::STRING}"
+    gem.add_development_dependency "rspec-mocks", ">= #{RSpec::Core::Version::STRING}"
     gem.add_development_dependency('cucumber', '>= 0.5.3')
     gem.add_development_dependency('autotest', '>= 4.2.9')
     gem.post_install_message = <<-EOM
@@ -43,14 +43,14 @@ end
 namespace :gem do
   desc "push to gemcutter"
   task :push => :build do
-    system "gem push pkg/rspec-core-#{Rspec::Core::Version::STRING}.gem"
+    system "gem push pkg/rspec-core-#{RSpec::Core::Version::STRING}.gem"
   end
 end
 
-Rspec::Core::RakeTask.new(:spec)
+RSpec::Core::RakeTask.new(:spec)
 
 desc "Run all examples using rcov"
-Rspec::Core::RakeTask.new :rcov => :cleanup_rcov_files do |t|
+RSpec::Core::RakeTask.new :rcov => :cleanup_rcov_files do |t|
   t.rcov = true
   t.rcov_opts =  %[-Ilib -Ispec --exclude "mocks,expectations,gems/*,spec/resources,spec/lib,spec/spec_helper.rb,db/*,/Library/Ruby/*,config/*"]
   t.rcov_opts << %[--no-html --aggregate coverage.data]
@@ -85,7 +85,7 @@ end
 
 Rake::RDocTask.new do |rdoc|
   rdoc.rdoc_dir = 'rdoc'
-  rdoc.title = "rspec-core #{Rspec::Core::Version::STRING}"
+  rdoc.title = "rspec-core #{RSpec::Core::Version::STRING}"
   rdoc.rdoc_files.include('README*')
   rdoc.rdoc_files.include('lib/**/*.rb')
 end

data/Upgrade.markdown

@@ -2,16 +2,16 @@
 
 ## What's changed
 
-### Rspec namespace
+### RSpec namespace
 
-The root namespace is now `Rspec` instead of `Spec`, and the root directory
+The root namespace is now `RSpec` instead of `Spec`, and the root directory
 under `lib` is `rspec` instead of `spec`.
 
 ### Configuration
 
 Typically in `spec/spec_helper.rb`, configuration is now done like this:
 
-    Rspec.configure do |c|
+    RSpec.configure do |c|
       # ....
     end
 
@@ -38,7 +38,7 @@ each example in a variety of ways.
 The most obvious use is for filtering the run. For example:
 
     # in spec/spec_helper.rb
-    Rspec.configure do |c|
+    RSpec.configure do |c|
       c.filter_run :focus => true
     end
 
@@ -54,7 +54,7 @@ When you run the `rspec` command, rspec will run only the examples that have
 
 You can also add `run_all_when_everything_filtered` to the config:
 
-    Rspec.configure do |c|
+    RSpec.configure do |c|
       c.filter_run :focus => true
       c.run_all_when_everything_filtered = true
     end
@@ -72,7 +72,7 @@ rspec-core, and here's how we're getting the right stuff to run under the
 right version:
 
     # in spec/spec_helper.rb
-    Rspec.configure do |c|
+    RSpec.configure do |c|
       c.exclusion_filter = { :ruby => lambda {|version|
         !(RUBY_VERSION.to_s =~ /^#{version.to_s}/)
       }}

data/VERSION

@@ -1 +1 @@
-2.0.0.beta.8
+2.0.0.beta.9

data/cucumber.yml

@@ -1,7 +1,2 @@
-<%
-rerun = File.file?('rerun.txt') ? IO.read('rerun.txt') : ""
-rerun_opts = rerun.to_s.strip.empty? ? "--format progress features" : "--format #{ENV['CUCUMBER_FORMAT'] || 'pretty'} #{rerun}"
-std_opts = "#{rerun_opts} --require features --format rerun --out rerun.txt --strict --tags ~@wip"
-%>
-default: <%= std_opts %>
-wip: --require features --tags @wip:3 --wip features
+default: --require features --strict --format progress --tags ~@wip features
+wip:     --require features --tags @wip:3 --wip features

data/example_specs/passing/subject_example.rb

@@ -0,0 +1,45 @@
+require File.dirname(__FILE__) + '/spec_helper'
+
+module SubjectExample
+  class OneThing
+    attr_accessor :what_things_do
+    def initialize
+      self.what_things_do = "stuff"
+    end
+  end
+
+  # implicit subject
+  describe OneThing do
+    it "should do what things do" do
+      subject.what_things_do.should == "stuff"
+    end
+    it "should be a OneThing" do
+      should == subject
+    end
+    its(:what_things_do) { should == "stuff" }
+  end
+
+  # explicit subject
+  describe SubjectExample::OneThing do
+    subject { SubjectExample::OneThing.new }
+    it "should do what things do" do
+      subject.what_things_do.should == "stuff"
+    end
+    it "should be a OneThing" do
+      should == subject
+    end
+    its(:what_things_do) { should == "stuff" }
+  end
+
+  # modified subject
+  describe OneThing do
+    subject { SubjectExample::OneThing.new }
+    before { subject.what_things_do = "more stuff" }
+    it "should do what things do" do
+      subject.what_things_do.should == "more stuff"
+    end
+    its(:what_things_do) { should == "more stuff" }
+  end
+
+end
+

data/example_specs/spec_helper.rb

@@ -4,7 +4,7 @@ $LOAD_PATH << File.expand_path('../../../rspec-mocks/lib', __FILE__)
 require 'rspec/expectations'
 require 'rspec/core'
 
-Rspec.configure do |c|
+RSpec.configure do |c|
   c.mock_with :rspec
 end
 

data/features/command_line/line_number_appended_to_path.feature

@@ -28,80 +28,78 @@ Feature: line number appended to file path
       end
       """
 
-@wip
   Scenario: nested groups - outer group on declaration line
-    When I run "rspec example_spec.rb:1 --format doc"
+    When I run "rspec ./example_spec.rb:1 --format doc"
     Then I should see "3 examples, 0 failures"
     And I should see "second example in outer group"
     And I should see "first example in outer group"
     And I should see "example in nested group"
 
-@wip
   Scenario: nested groups - outer group inside block before example
-    When I run "rspec example_spec.rb:2 --format doc"
+    When I run "rspec ./example_spec.rb:2 --format doc"
     Then I should see "3 examples, 0 failures"
     And I should see "second example in outer group"
     And I should see "first example in outer group"
     And I should see "example in nested group"
 
   Scenario: nested groups - inner group on declaration line
-    When I run "rspec example_spec.rb:11 --format doc"
+    When I run "rspec ./example_spec.rb:11 --format doc"
     Then I should see "1 example, 0 failures"
     And I should see "example in nested group"
     And I should not see "second example in outer group"
     And I should not see "first example in outer group"
 
   Scenario: nested groups - inner group inside block before example
-    When I run "rspec example_spec.rb:12 --format doc"
+    When I run "rspec ./example_spec.rb:12 --format doc"
     Then I should see "1 example, 0 failures"
     And I should see "example in nested group"
     And I should not see "second example in outer group"
     And I should not see "first example in outer group"
 
   Scenario: two examples - first example on declaration line
-    When I run "rspec example_spec.rb:3 --format doc"
+    When I run "rspec ./example_spec.rb:3 --format doc"
     Then I should see "1 example, 0 failures"
     And I should see "first example in outer group"
     But I should not see "second example in outer group"
     And I should not see "example in nested group"
 
   Scenario: two examples - first example inside block
-    When I run "rspec example_spec.rb:4 --format doc"
+    When I run "rspec ./example_spec.rb:4 --format doc"
     Then I should see "1 example, 0 failures"
     And I should see "first example in outer group"
     But I should not see "second example in outer group"
     And I should not see "example in nested group"
 
   Scenario: two examples - first example on end
-    When I run "rspec example_spec.rb:5 --format doc"
+    When I run "rspec ./example_spec.rb:5 --format doc"
     Then I should see "1 example, 0 failures"
     And I should see "first example in outer group"
     But I should not see "second example in outer group"
     And I should not see "example in nested group"
 
   Scenario: two examples - first example after end but before next example
-    When I run "rspec example_spec.rb:6 --format doc"
+    When I run "rspec ./example_spec.rb:6 --format doc"
     Then I should see "1 example, 0 failures"
     And I should see "first example in outer group"
     But I should not see "second example in outer group"
     And I should not see "example in nested group"
 
   Scenario: two examples - second example on declaration line
-    When I run "rspec example_spec.rb:7 --format doc"
+    When I run "rspec ./example_spec.rb:7 --format doc"
     Then I should see "1 example, 0 failures"
     And I should see "second example in outer group"
     But I should not see "first example in outer group"
     And I should not see "example in nested group"
 
   Scenario: two examples - second example inside block
-    When I run "rspec example_spec.rb:7 --format doc"
+    When I run "rspec ./example_spec.rb:7 --format doc"
     Then I should see "1 example, 0 failures"
     And I should see "second example in outer group"
     But I should not see "first example in outer group"
     And I should not see "example in nested group"
 
   Scenario: two examples - second example on end
-    When I run "rspec example_spec.rb:7 --format doc"
+    When I run "rspec ./example_spec.rb:7 --format doc"
     Then I should see "1 example, 0 failures"
     And I should see "second example in outer group"
     But I should not see "first example in outer group"

data/features/command_line/line_number_option.feature

@@ -1,6 +1,6 @@
 Feature: line number option
 
-  As an Rspec user
+  As an RSpec user
   I want to run one example identified by the line number
   
   Scenario: standard examples
@@ -20,7 +20,7 @@ Feature: line number option
         
       end
       """
-    When I run "rspec example_spec.rb --line 5 --format doc"
+    When I run "rspec ./example_spec.rb --line 5 --format doc"
     Then I should see "1 example, 0 failures"
     Then I should see "should be > 8"
     But the stdout should not contain "should be < 10"
@@ -38,7 +38,7 @@ Feature: line number option
         
       end
       """
-    When I run "rspec example_spec.rb --line 5 --format doc"
+    When I run "rspec ./example_spec.rb --line 5 --format doc"
     Then I should see "1 example, 0 failures"
     Then I should see "should be > 8"
     But the stdout should not contain "should be < 10"

data/features/configuration/custom_options.feature

@@ -0,0 +1,71 @@
+Feature: custom options
+
+  In order to seamlessly provide my users more options
+  As an RSpec extenstion-library author
+  I want to define new options on the RSpec.configuration
+
+  Scenario: boolean option with default settings
+    Given a file named "boolean_option_spec.rb" with:
+      """
+      RSpec.configure do |c|
+        c.add_option :custom_option, :type => :boolean
+      end
+
+      describe "custom option" do
+        it "is false by default" do
+          RSpec.configuration.custom_option.should be_false
+        end
+
+        it "is exposed as a predicate" do
+          RSpec.configuration.custom_option?.should be_false
+        end
+      end
+      """
+    When I run "rspec ./boolean_option_spec.rb"
+    Then I should see "2 examples, 0 failures"
+
+  Scenario: boolean option set to default to true
+    Given a file named "boolean_option_spec.rb" with:
+      """
+      RSpec.configure do |c|
+        c.add_option :custom_option, :type => :boolean, :default => true
+      end
+
+      describe "custom option" do
+        it "is true by default" do
+          RSpec.configuration.custom_option.should be_true
+        end
+
+        it "is exposed as a predicate" do
+          RSpec.configuration.custom_option?.should be_true
+        end
+      end
+      """
+    When I run "rspec ./boolean_option_spec.rb"
+    Then I should see "2 examples, 0 failures"
+
+@wip
+  Scenario: boolean option overridden in client app
+    Given a file named "boolean_option_spec.rb" with:
+      """
+      RSpec.configure do |c|
+        c.add_option :custom_option, :type => :boolean
+      end
+
+      RSpec.configure do |c|
+        c.custom_option = true
+      end
+
+      describe "custom option" do
+        it "returns the value set in the client app" do
+          RSpec.configuration.custom_option.should be_true
+        end
+
+        it "is exposed as a predicate" do
+          RSpec.configuration.custom_option?.should be_true
+        end
+      end
+      """
+    When I run "rspec ./boolean_option_spec.rb"
+    Then I should see "2 examples, 0 failures"
+

data/features/configuration/options_file.feature

@@ -5,22 +5,22 @@ Feature: spec/spec.opts
   automatically.
 
   Options declared in spec/spec.opts will override configuration
-  set up in Rspec.configure blocks.
+  set up in RSpec.configure blocks.
 
-  Scenario: color set in Rspec.configure
+  Scenario: color set in RSpec.configure
     Given a file named "spec/example_spec.rb" with:
       """
-      Rspec.configure {|c| c.color_enabled = true }
+      RSpec.configure {|c| c.color_enabled = true }
 
       describe "color_enabled" do
-        context "when set with Rspec.configure" do
+        context "when set with RSpec.configure" do
           it "is true" do
-            Rspec.configuration.color_enabled?.should be_true
+            RSpec.configuration.color_enabled?.should be_true
           end
         end
       end
       """
-    When I run "rspec spec/example_spec.rb"
+    When I run "rspec ./spec/example_spec.rb"
     Then I should see "1 example, 0 failures"
             
   Scenario: color set in .rspec
@@ -31,14 +31,14 @@ Feature: spec/spec.opts
     And a file named "spec/example_spec.rb" with:
       """
       describe "color_enabled" do
-        context "when set with Rspec.configure" do
+        context "when set with RSpec.configure" do
           it "is true" do
-            Rspec.configuration.color_enabled?.should be_true
+            RSpec.configuration.color_enabled?.should be_true
           end
         end
       end
       """
-    When I run "rspec spec/example_spec.rb"
+    When I run "rspec ./spec/example_spec.rb"
     Then I should see "1 example, 0 failures"
 
 @wip            
@@ -49,20 +49,20 @@ Feature: spec/spec.opts
       """
     And a file named "spec/spec_helper.rb" with:
       """
-      Rspec.configure {|c| c.formatter = 'progress'}
+      RSpec.configure {|c| c.formatter = 'progress'}
       """
     And a file named "spec/example_spec.rb" with:
       """
       require "spec_helper"
 
       describe "formatter" do
-        context "when set with Rspec.configure and in spec.opts" do
+        context "when set with RSpec.configure and in spec.opts" do
           it "takes the value set in spec.opts" do
-            Rspec.configuration.formatter.should be_an(Rspec::Core::Formatters::DocumentationFormatter)
+            RSpec.configuration.formatter.should be_an(RSpec::Core::Formatters::DocumentationFormatter)
           end
         end
       end
       """
-    When I run "rspec spec/example_spec.rb"
+    When I run "rspec ./spec/example_spec.rb"
     Then I should see "1 example, 0 failures"