rspec-core 2.0.0.beta.22 → 2.6.4

data/features/command_line/format_option.feature

@@ -0,0 +1,73 @@
+Feature: --format option
+
+  Use the --format option to tell RSpec how to format the output.
+
+  RSpec ships with a few formatters built in. By default, it uses the progress
+  formatter, which generates output like this:
+
+      ....F.....*.....
+
+  A '.' represents a passing example, 'F' is failing, and '*' is pending.
+
+  To see the documentation strings passed to each describe(), context(), and it()
+  method, use the documentation formatter:
+
+      $ rspec spec --format documentation
+
+  You can also specify an output target (STDOUT by default) by appending a
+  filename to the argument:
+
+    $ rspec spec --format documentation:rspec.output.txt
+
+  Background:
+    Given a file named "example_spec.rb" with:
+      """
+      describe "something" do
+        it "does something that passes" do
+          5.should eq(5)
+        end
+
+        it "does something that fails" do
+          5.should eq(4)
+        end
+
+        it "does something that is pending", :pending => true do
+          5.should be > 3
+        end
+      end
+      """
+
+  Scenario: progress bar format (default)
+    When I run `rspec example_spec.rb`
+    Then the output should contain ".F*"
+
+  Scenario: documentation format
+    When I run `rspec example_spec.rb --format documentation`
+    Then the output should contain:
+      """
+      something
+        does something that passes
+        does something that fails (FAILED - 1)
+        does something that is pending (PENDING: Not Yet Implemented)
+      """
+
+  Scenario: documentation format saved to a file
+    When I run `rspec example_spec.rb --format documentation --out rspec.txt`
+    Then the file "rspec.txt" should contain:
+      """
+      something
+        does something that passes
+        does something that fails (FAILED - 1)
+        does something that is pending (PENDING: Not Yet Implemented)
+      """
+
+  Scenario: multiple formats
+    When I run `rspec example_spec.rb --format progress --format documentation --out rspec.txt`
+    Then the output should contain ".F*"
+    And the file "rspec.txt" should contain:
+      """
+      something
+        does something that passes
+        does something that fails (FAILED - 1)
+        does something that is pending (PENDING: Not Yet Implemented)
+      """

data/features/command_line/line_number_appended_to_path.feature

@@ -1,8 +1,8 @@
 Feature: line number appended to file path
 
-  As an RSpec user
-  I want to run one example identified by the 
-    line number appended to the filepath
+  To run a single example or group, you can append the line number to the path, e.g.
+
+      rspec path/to/example_spec.rb:37
   
   Background:
     Given a file named "example_spec.rb" with:
@@ -29,80 +29,78 @@ Feature: line number appended to file path
       """
 
   Scenario: nested groups - outer group on declaration line
-    When I run "rspec ./example_spec.rb:1 --format doc"
-    Then the output should contain "3 examples, 0 failures"
+    When I run `rspec example_spec.rb:1 --format doc`
+    Then the examples should all pass
     And the output should contain "second example in outer group"
     And the output should contain "first example in outer group"
     And the output should contain "example in nested group"
 
   Scenario: nested groups - outer group inside block before example
-    When I run "rspec ./example_spec.rb:2 --format doc"
-    Then the output should contain "3 examples, 0 failures"
+    When I run `rspec example_spec.rb:2 --format doc`
+    Then the examples should all pass
     And the output should contain "second example in outer group"
     And the output should contain "first example in outer group"
     And the output should contain "example in nested group"
 
   Scenario: nested groups - inner group on declaration line
-    When I run "rspec ./example_spec.rb:11 --format doc"
-    Then the output should contain "1 example, 0 failures"
+    When I run `rspec example_spec.rb:11 --format doc`
+    Then the examples should all pass
     And the output should contain "example in nested group"
     And the output should not contain "second example in outer group"
     And the output should not contain "first example in outer group"
 
   Scenario: nested groups - inner group inside block before example
-    When I run "rspec ./example_spec.rb:12 --format doc"
-    Then the output should contain "1 example, 0 failures"
+    When I run `rspec example_spec.rb:12 --format doc`
+    Then the examples should all pass
     And the output should contain "example in nested group"
     And the output should not contain "second example in outer group"
     And the output should not contain "first example in outer group"
 
   Scenario: two examples - first example on declaration line
-    When I run "rspec ./example_spec.rb:3 --format doc"
-    Then the output should contain "1 example, 0 failures"
+    When I run `rspec example_spec.rb:3 --format doc`
+    Then the examples should all pass
     And the output should contain "first example in outer group"
     But the output should not contain "second example in outer group"
     And the output should not contain "example in nested group"
 
   Scenario: two examples - first example inside block
-    When I run "rspec ./example_spec.rb:4 --format doc"
-    Then the output should contain "1 example, 0 failures"
+    When I run `rspec example_spec.rb:4 --format doc`
+    Then the examples should all pass
     And the output should contain "first example in outer group"
     But the output should not contain "second example in outer group"
     And the output should not contain "example in nested group"
 
   Scenario: two examples - first example on end
-    When I run "rspec ./example_spec.rb:5 --format doc"
-    Then the output should contain "1 example, 0 failures"
+    When I run `rspec example_spec.rb:5 --format doc`
+    Then the examples should all pass
     And the output should contain "first example in outer group"
     But the output should not contain "second example in outer group"
     And the output should not contain "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"
-    Then the output should contain "1 example, 0 failures"
+    When I run `rspec example_spec.rb:6 --format doc`
+    Then the examples should all pass
     And the output should contain "first example in outer group"
     But the output should not contain "second example in outer group"
     And the output should not contain "example in nested group"
 
   Scenario: two examples - second example on declaration line
-    When I run "rspec ./example_spec.rb:7 --format doc"
-    Then the output should contain "1 example, 0 failures"
+    When I run `rspec example_spec.rb:7 --format doc`
+    Then the examples should all pass
     And the output should contain "second example in outer group"
     But the output should not contain "first example in outer group"
     And the output should not contain "example in nested group"
 
   Scenario: two examples - second example inside block
-    When I run "rspec ./example_spec.rb:7 --format doc"
-    Then the output should contain "1 example, 0 failures"
+    When I run `rspec example_spec.rb:7 --format doc`
+    Then the examples should all pass
     And the output should contain "second example in outer group"
     But the output should not contain "first example in outer group"
     And the output should not contain "example in nested group"
 
   Scenario: two examples - second example on end
-    When I run "rspec ./example_spec.rb:7 --format doc"
-    Then the output should contain "1 example, 0 failures"
+    When I run `rspec example_spec.rb:7 --format doc`
+    Then the examples should all pass
     And the output should contain "second example in outer group"
     But the output should not contain "first example in outer group"
     And the output should not contain "example in nested group"
-
-

data/features/command_line/line_number_option.feature

@@ -1,8 +1,9 @@
-Feature: line number option
+Feature: --line_number option
+
+  To run a single example or group, you can use the --line_number option:
+
+      rspec path/to/example_spec.rb --line_number 37
 
-  As an RSpec user
-  I want to run one example identified by the line number
-  
   Scenario: standard examples
     Given a file named "example_spec.rb" with:
       """
@@ -20,10 +21,10 @@ Feature: line number option
         
       end
       """
-    When I run "rspec ./example_spec.rb --line 5 --format doc"
-    Then the output should contain "1 example, 0 failures"
+    When I run `rspec example_spec.rb --line_number 5 --format doc`
+    Then the examples should all pass
     Then the output should contain "should be > 8"
-    But the stdout should not contain "should be < 10"
+    But the output should not contain "should be < 10"
 
   Scenario: one liner
     Given a file named "example_spec.rb" with:
@@ -38,7 +39,7 @@ Feature: line number option
         
       end
       """
-    When I run "rspec ./example_spec.rb --line 5 --format doc"
-    Then the output should contain "1 example, 0 failures"
+    When I run `rspec example_spec.rb --line_number 5 --format doc`
+    Then the examples should all pass
     Then the output should contain "should be > 8"
-    But the stdout should not contain "should be < 10"
+    But the output should not contain "should be < 10"

data/features/command_line/rake_task.feature

@@ -0,0 +1,68 @@
+Feature: rake task
+  
+  RSpec ships with a rake task with a number of useful options
+
+  Scenario: default options with passing spec (prints command and exit status is 0)
+    Given a file named "Rakefile" with:
+      """
+      require 'rspec/core/rake_task'
+
+      RSpec::Core::RakeTask.new(:spec)
+
+      task :default => :spec
+      """
+    And a file named "spec/thing_spec.rb" with:
+      """
+      describe "something" do
+        it "does something" do
+          # pass
+        end
+      end
+      """
+    When I run `rake`
+    Then the stderr should contain "ruby -S rspec"
+    Then the exit status should be 0
+
+  Scenario: default options with failing spec (exit status is 1)
+    Given a file named "Rakefile" with:
+      """
+      require 'rspec/core/rake_task'
+
+      RSpec::Core::RakeTask.new(:spec)
+
+      task :default => :spec
+      """
+    And a file named "spec/thing_spec.rb" with:
+      """
+      describe "something" do
+        it "does something" do
+          fail
+        end
+      end
+      """
+    When I run `rake`
+    Then the exit status should be 1
+      
+  Scenario: fail_on_error = false with failing spec (exit status is 0)
+    Given a file named "Rakefile" with:
+      """
+      require 'rspec/core/rake_task'
+
+      RSpec::Core::RakeTask.new(:spec) do |t|
+        t.fail_on_error = false
+      end
+
+      task :default => :spec
+      """
+    And a file named "spec/thing_spec.rb" with:
+      """
+      describe "something" do
+        it "does something" do
+          fail
+        end
+      end
+      """
+    When I run `rake`
+    Then the exit status should be 0
+      
+

data/features/command_line/tag.feature

@@ -0,0 +1,90 @@
+Feature: --tag option
+
+  Use the --tag (or -t) option to filter the examples by tags.
+  
+  The tag can be a simple name or a name:value pair. In the first case,
+  examples with :name => true will be filtered. In the second case, examples
+  with :name => value will be filtered, where value is always a string.  In
+  both cases, name is converted to a symbol.
+  
+  Tags can also be used to exclude examples by adding a ~ before the tag.  For
+  example ~tag will exclude all examples marked with :tag => true and
+  ~tag:value will exclude all examples marked with :tag => value.
+  
+  To be compatible with the Cucumber syntax, tags can optionally start with
+  an @ symbol, which will be ignored.
+
+  Background:
+    Given a file named "tagged_spec.rb" with:
+      """
+      describe "group with tagged specs" do
+        it "example I'm working now", :focus => true do; end
+        it "special example with string", :type => 'special' do; end
+        it "special example with symbol", :type => :special do; end
+        it "slow example", :skip => true do; end
+        it "ordinary example", :speed => 'slow' do; end
+        it "untagged example" do; end
+      end
+      """
+
+  Scenario: filter examples with non-existent tag
+    When I run `rspec . --tag mytag`
+    And the examples should all pass
+
+  Scenario: filter examples with a simple tag
+    When I run `rspec . --tag focus`
+    Then the output should contain "Run filtered including {:focus=>true}"
+    And the examples should all pass
+
+  Scenario: filter examples with a simple tag and @
+    When I run `rspec . --tag @focus`
+    Then the output should contain "Run filtered including {:focus=>true}"
+    Then the examples should all pass
+
+  Scenario: filter examples with a name:value tag
+    When I run `rspec . --tag type:special`
+    Then the output should contain:
+      """
+      Run filtered including {:type=>"special"}
+      """
+    And the output should contain "2 examples"
+    And the examples should all pass
+  
+  Scenario: filter examples with a name:value tag and @
+    When I run `rspec . --tag @type:special`
+    Then the output should contain:
+      """
+      Run filtered including {:type=>"special"}
+      """
+    And the examples should all pass
+  
+  Scenario: exclude examples with a simple tag
+    When I run `rspec . --tag ~skip`
+    Then the output should contain "Run filtered excluding {:skip=>true}"
+    Then the examples should all pass
+
+  Scenario: exclude examples with a simple tag and @
+    When I run `rspec . --tag ~@skip`
+    Then the output should contain "Run filtered excluding {:skip=>true}"
+    Then the examples should all pass
+    
+  Scenario: exclude examples with a name:value tag
+    When I run `rspec . --tag ~speed:slow`
+    Then the output should contain:
+      """
+      Run filtered excluding {:speed=>"slow"}
+      """
+    Then the examples should all pass
+  
+  Scenario: exclude examples with a name:value tag and @
+    When I run `rspec . --tag ~@speed:slow`
+    Then the output should contain:
+      """
+      Run filtered excluding {:speed=>"slow"}
+      """
+    Then the examples should all pass
+
+  Scenario: filter examples with a simple tag, exclude examples with another tag
+    When I run `rspec . --tag focus --tag ~skip`
+    Then the output should contain "Run filtered including {:focus=>true}, excluding {:skip=>true}"
+    And the examples should all pass

data/features/configuration/alias_example_to.feature

@@ -0,0 +1,48 @@
+Feature: alias_example_to
+
+  Use `config.alias_example_to` to create new example group methods
+  that define examples with the configured metadata.
+
+  If you set the `treat_symbols_as_metadata_keys_with_true_values` config option
+  to `true`, you can specify metadata using only symbols.
+
+  Scenario: Use alias_example_to to define focused example
+    Given a file named "alias_example_to_spec.rb" with:
+      """
+      RSpec.configure do |c|
+        c.alias_example_to :fit, :focused => true
+        c.filter_run :focused => true
+      end
+
+      describe "an example group" do
+        it "does one thing" do
+        end
+
+        fit "does another thing" do
+        end
+      end
+      """
+    When I run `rspec alias_example_to_spec.rb --format doc`
+    Then the output should contain "does another thing"
+    And the output should not contain "does one thing"
+
+  Scenario: use symbols as metadata
+    Given a file named "use_symbols_as_metadata_spec.rb" with:
+      """
+      RSpec.configure do |c|
+        c.treat_symbols_as_metadata_keys_with_true_values = true
+        c.alias_example_to :fit, :focused
+        c.filter_run :focused
+      end
+
+      describe "an example group" do
+        it "does one thing" do
+        end
+
+        fit "does another thing" do
+        end
+      end
+      """
+    When I run `rspec use_symbols_as_metadata_spec.rb --format doc`
+    Then the output should contain "does another thing"
+    And the output should not contain "does one thing"

data/features/configuration/custom_settings.feature

@@ -1,10 +1,8 @@
 Feature: custom settings
 
-  In order to seamlessly provide users more configuration settings
-  As an RSpec extenstion-library author
-  I want to define new settings on the RSpec.configuration object
+  Extensions like rspec-rails can add their own configuration settings.
 
-  Scenario: simple setting
+  Scenario: simple setting (with defaults)
     Given a file named "additional_setting_spec.rb" with:
       """
       RSpec.configure do |c|
@@ -31,8 +29,8 @@ Feature: custom settings
         end
       end
       """
-    When I run "rspec ./additional_setting_spec.rb"
-    Then the output should contain "0 failures"
+    When I run `rspec ./additional_setting_spec.rb`
+    Then the examples should all pass
 
   Scenario: default to true
     Given a file named "additional_setting_spec.rb" with:
@@ -57,8 +55,8 @@ Feature: custom settings
         end
       end
       """
-    When I run "rspec ./additional_setting_spec.rb"
-    Then the output should contain "0 failures"
+    When I run `rspec ./additional_setting_spec.rb`
+    Then the examples should all pass
 
   Scenario: overridden in a subsequent RSpec.configure block
     Given a file named "additional_setting_spec.rb" with:
@@ -81,6 +79,6 @@ Feature: custom settings
         end
       end
       """
-    When I run "rspec ./additional_setting_spec.rb"
-    Then the output should contain "0 failures"
+    When I run `rspec ./additional_setting_spec.rb`
+    Then the examples should all pass
 

data/features/configuration/fail_fast.feature

@@ -0,0 +1,77 @@
+Feature: fail fast
+
+  Use the fail_fast option to tell RSpec to abort the run on first failure:
+
+      RSpec.configure {|c| c.fail_fast = true}
+
+  Background:
+    Given a file named "spec/spec_helper.rb" with:
+      """
+      RSpec.configure {|c| c.fail_fast = true}
+      """
+
+  Scenario: fail_fast with no failures (runs all examples)
+    Given a file named "spec/example_spec.rb" with:
+      """
+      describe "something" do
+        it "passes" do
+        end
+
+        it "passes too" do
+        end
+      end
+      """
+    When I run `rspec spec/example_spec.rb`
+    Then the examples should all pass
+
+  Scenario: fail_fast with first example failing (only runs the one example)
+    Given a file named "spec/example_spec.rb" with:
+      """
+      require "spec_helper"
+      describe "something" do
+        it "fails" do
+          fail
+        end
+
+        it "passes" do
+        end
+      end
+      """
+    When I run `rspec spec/example_spec.rb -fd`
+    Then the output should contain "1 example, 1 failure"
+
+  Scenario: fail_fast with multiple files, second example failing (only runs the first two examples)
+    Given a file named "spec/example_1_spec.rb" with:
+      """
+      require "spec_helper"
+      describe "something" do
+        it "passes" do
+        end
+
+        it "fails" do
+          fail
+        end
+      end
+
+      describe "something else" do
+        it "fails" do
+          fail
+        end
+      end
+      """
+    And a file named "spec/example_2_spec.rb" with:
+      """
+      require "spec_helper"
+      describe "something" do
+        it "passes" do
+        end
+      end
+
+      describe "something else" do
+        it "fails" do
+          fail
+        end
+      end
+      """
+    When I run `rspec spec`
+    Then the output should contain "2 examples, 1 failure"

data/features/configuration/read_options_from_file.feature

@@ -1,17 +1,14 @@
 Feature: read command line configuration options from files
 
-  RSpec will read command line configuration options from files in
-  two different locations:
+  RSpec reads command line configuration options from files in two different
+  locations:
   
     Local:  "./.rspec" (i.e. in the project's root directory)
     Global: "~/.rspec" (i.e. in the user's home directory)
 
   Options declared in the local file override those in the global file, while
   those declared in RSpec.configure will override any ".rspec" file.
-  
-  NOTE: For backwards compatibility with rspec-1, you can write command line
-  options in a "spec/spec.opts" file and it will be loaded automatically.
-            
+
   Scenario: color set in .rspec
     Given a file named ".rspec" with:
       """
@@ -21,39 +18,58 @@ Feature: read command line configuration options from files
       """
       describe "color_enabled" do
         context "when set with RSpec.configure" do
+          before do
+            # color is disabled for non-tty output, so stub the output stream
+            # to say it is tty, even though we're running this with cucumber
+            RSpec.configuration.output_stream.stub(:tty?) { true }
+          end
+
           it "is true" do
             RSpec.configuration.should be_color_enabled
           end
         end
       end
       """
-    When I run "rspec ./spec/example_spec.rb"
-    Then the output should contain "1 example, 0 failures"
+    When I run `rspec ./spec/example_spec.rb`
+    Then the examples should all pass
 
-  Scenario: formatter set in RSpec.configure overrides .rspec
-    Given a file named ".rspec" with:
+  Scenario: custom options file
+    Given a file named "my.options" with:
+      """
+      --format documentation
+      """
+    And a file named "spec/example_spec.rb" with:
+      """
+      describe "formatter set in custom options file" do
+        it "sets formatter" do
+          RSpec.configuration.formatters.first.
+            should be_a(RSpec::Core::Formatters::DocumentationFormatter)
+        end
+      end
       """
-      --format progress
+    When I run `rspec spec/example_spec.rb --options my.options`
+    Then the examples should all pass
+
+  Scenario: RSpec ignores ./.rspec when custom options file is used
+    Given a file named "my.options" with:
       """
-    And a file named "spec/spec_helper.rb" with:
+      --format documentation
       """
-      RSpec.configure {|c| c.formatter = 'documentation'}
+    And a file named ".rspec" with:
+      """
+      --color
       """
     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
-          it "takes the value set in spec.opts" do
-            RSpec.configuration.formatter.should be_an(RSpec::Core::Formatters::DocumentationFormatter)
-          end
+      describe "custom options file" do
+        it "causes .rspec to be ignored" do
+          RSpec.configuration.color_enabled.should be_false
         end
       end
       """
-    When I run "rspec ./spec/example_spec.rb"
-    Then the output should contain "1 example, 0 failures"
-    
+    When I run `rspec spec/example_spec.rb --options my.options`
+    Then the examples should all pass
+
   Scenario: using ERB in .rspec
     Given a file named ".rspec" with:
       """
@@ -63,9 +79,9 @@ Feature: read command line configuration options from files
       """
       describe "formatter" do
         it "is set to documentation" do
-          RSpec.configuration.formatter.should be_an(RSpec::Core::Formatters::DocumentationFormatter)
+          RSpec.configuration.formatters.first.should be_an(RSpec::Core::Formatters::DocumentationFormatter)
         end
       end
       """
-    When I run "rspec ./spec/example_spec.rb"
-    Then the output should contain "1 example, 0 failures"
+    When I run `rspec ./spec/example_spec.rb`
+    Then the examples should all pass