rspec-core 2.11.1 → 3.11.0

data/features/command_line/format_option.feature

@@ -1,81 +0,0 @@
-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
-
-  `rspec --help` lists available formatters:
-
-      [p]rogress (default - dots)
-      [d]ocumentation (group and example names)
-      [h]tml
-      [t]extmate
-      custom formatter class name
-
-  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 --format progress 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: No reason given)
-      """
-
-  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: No reason given)
-      """
-
-  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: No reason given)
-      """

data/features/command_line/init.feature

@@ -1,18 +0,0 @@
-Feature: --init option
-
-  Use the --init option on the command line to generate conventional
-  files for an rspec project.
-
-  Scenario: generate .rspec
-    When I run `rspec --init`
-    Then the following files should exist:
-      | .rspec |
-    And the output should contain "create   .rspec"
-
-  Scenario: .rspec file already exists
-    Given a file named ".rspec" with:
-      """
-      --color
-      """
-    When I run `rspec --init`
-    Then the output should contain "exist   .rspec"

data/features/command_line/line_number_appended_to_path.feature

@@ -1,140 +0,0 @@
-Feature: line number appended to file path
-
-  To run one or more examples or groups, 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:
-      """
-      describe "outer group" do
-
-        it "first example in outer group" do
-
-        end
-        
-        it "second example in outer group" do
-
-        end
-
-        describe "nested group" do
-          
-          it "example in nested group" do
-
-          end
-        
-        end
-
-      end
-      """
-    And a file named "example2_spec.rb" with:
-      """
-      describe "yet another group" do
-        it "first example in second file" do
-        end
-        it "second example in second file" do
-        end
-      end
-      """
-
-  Scenario: nested groups - outer group on declaration line
-    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 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 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 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 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 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 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 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 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 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 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: specified multiple times for different files
-    When I run `rspec example_spec.rb:7 example2_spec.rb:4 --format doc`
-    Then the examples should all pass
-    And the output should contain "second example in outer group"
-    And the output should contain "second example in second file"
-    But the output should not contain "first example in outer group"
-    And the output should not contain "nested group"
-    And the output should not contain "first example in second file"
-
-  Scenario: specified multiple times for the same file with multiple arguments
-    When I run `rspec example_spec.rb:7 example_spec.rb:11 --format doc`
-    Then the examples should all pass
-    And the output should contain "second example in outer group"
-    And the output should contain "nested group"
-    But the output should not contain "first example in outer group"
-    And the output should not contain "second file"
-
-  Scenario: specified multiple times for the same file with a single argument
-    When I run `rspec example_spec.rb:7:11 --format doc`
-    Then the examples should all pass
-    And the output should contain "second example in outer group"
-    And the output should contain "nested group"
-    But the output should not contain "first example in outer group"
-    And the output should not contain "second file"

data/features/command_line/line_number_option.feature

@@ -1,58 +0,0 @@
-Feature: --line_number option
-
-  To run a examples or groups by line numbers, one can use the --line_number option:
-
-      rspec path/to/example_spec.rb --line_number 37
-
-  This option can be specified multiple times.
-
-  Scenario: standard examples
-    Given a file named "example_spec.rb" with:
-      """
-      require "rspec/expectations"
-
-      describe 9 do
-
-        it "should be > 8" do
-          9.should be > 8
-        end
-
-        it "should be < 10" do
-          9.should be < 10
-        end
-
-        it "should be 3 squared" do
-          9.should be 3*3
-        end
-
-      end
-      """
-    When I run `rspec example_spec.rb --line_number 5 --format doc`
-    Then the examples should all pass
-    And the output should contain "should be > 8"
-    But the output should not contain "should be < 10"
-    And the output should not contain "should be 3*3"
-
-    When I run `rspec example_spec.rb --line_number 5 --line_number 9 --format doc`
-    Then the examples should all pass
-    And the output should contain "should be > 8"
-    And the output should contain "should be < 10"
-    But the output should not contain "should be 3*3"
-
-  Scenario: one liner
-    Given a file named "example_spec.rb" with:
-      """
-      require "rspec/expectations"
-
-      describe 9 do
-
-        it { should be > 8 }
-
-        it { should be < 10 }
-        
-      end
-      """
-    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 output should not contain "should be < 10"

data/features/command_line/order.feature

@@ -1,29 +0,0 @@
-Feature: --order (new in rspec-core-2.8)
-
-  Use the `--order` option to tell RSpec how to order the files, groups, and
-  examples. Options are `default` and `rand`:
-
-  Default is:
-
-    * files are ordered based on the underlying file system's order (typically
-      case-sensitive alpha on *nix OS's and case-insenstive alpha in Windows)
-    * groups/examples are loaded in the order in which they are declared
-
-  Use `rand` to randomize the order of files, groups within files, and
-  examples within groups.*
-
-  * Nested groups are always run from top-level to bottom-level in order to avoid
-    executing `before(:all)` and `after(:all)` hooks more than once, but the order
-    of groups at each level is randomized.
-
-  You can also specify a seed
-
-  <h3>Examples</h3>
-
-      --order default
-      --order rand
-      --order rand:123
-      --seed 123 # same as --order rand:123
-
-  The `default` option is only necessary when you have `--order rand` stored in a
-  config file (e.g. `.rspec`) and you want to override it from the command line.

data/features/command_line/pattern_option.feature

@@ -1,31 +0,0 @@
-Feature: pattern option
-
-  By default, RSpec loads files matching the pattern:
-
-      "spec/**/*_spec.rb"
-
-  Use the `--pattern` option to declare a different pattern.
-
-  Scenario: default pattern
-    Given a file named "spec/example_spec.rb" with:
-      """
-      describe "addition" do
-        it "adds things" do
-          (1 + 2).should eq(3)
-        end
-      end
-      """
-    When I run `rspec`
-    Then the output should contain "1 example, 0 failures"
-
-  Scenario: override the default pattern on the command line
-    Given a file named "spec/example.spec" with:
-      """
-      describe "addition" do
-        it "adds things" do
-          (1 + 2).should eq(3)
-        end
-      end
-      """
-    When I run `rspec --pattern "spec/**/*.spec"`
-    Then the output should contain "1 example, 0 failures"

data/features/command_line/rake_task.feature

@@ -1,68 +0,0 @@
-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 output 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/ruby.feature

@@ -1,22 +0,0 @@
-Feature: run with ruby command
-
-  You can use the `ruby` command to run specs. You just need to require
-  `rspec/autorun`. 
-  
-  Generally speaking, you're better off using the `rspec` command, which
-  requires `rspec/autorun` for you, but some tools only work with the `ruby`
-  command.
-
-  Scenario:
-    Given a file named "example_spec.rb" with:
-      """
-      require 'rspec/autorun'
-
-      describe 1 do
-        it "is < 2" do
-          1.should be < 2
-        end
-      end
-      """
-    When I run `ruby example_spec.rb`
-    Then the output should contain "1 example, 0 failures"

data/features/command_line/tag.feature

@@ -1,91 +0,0 @@
-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 "include {: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 "include {: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:
-      """
-      include {: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:
-      """
-      include {: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 "exclude {: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 "exclude {: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:
-      """
-      exclude {: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:
-      """
-      exclude {: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 "include {:focus=>true}"
-    And the output should contain "exclude {:skip=>true}"
-    And the examples should all pass

data/features/configuration/alias_example_to.feature

@@ -1,48 +0,0 @@
-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,84 +0,0 @@
-Feature: custom settings
-
-  Extensions like rspec-rails can add their own configuration settings.
-
-  Scenario: simple setting (with defaults)
-    Given a file named "additional_setting_spec.rb" with:
-      """
-      RSpec.configure do |c|
-        c.add_setting :custom_setting
-      end
-
-      describe "custom setting" do
-        it "is nil by default" do
-          RSpec.configuration.custom_setting.should be_nil
-        end
-
-        it "acts false by default" do
-          RSpec.configuration.custom_setting.should be_false
-        end
-
-        it "is exposed as a predicate" do
-          RSpec.configuration.custom_setting?.should be_false
-        end
-
-        it "can be overridden" do
-          RSpec.configuration.custom_setting = true
-          RSpec.configuration.custom_setting.should be_true
-          RSpec.configuration.custom_setting?.should be_true
-        end
-      end
-      """
-    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:
-      """
-      RSpec.configure do |c|
-        c.add_setting :custom_setting, :default => true
-      end
-
-      describe "custom setting" do
-        it "is true by default" do
-          RSpec.configuration.custom_setting.should be_true
-        end
-
-        it "is exposed as a predicate" do
-          RSpec.configuration.custom_setting?.should be_true
-        end
-
-        it "can be overridden" do
-          RSpec.configuration.custom_setting = false
-          RSpec.configuration.custom_setting.should be_false
-          RSpec.configuration.custom_setting?.should be_false
-        end
-      end
-      """
-    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:
-      """
-      RSpec.configure do |c|
-        c.add_setting :custom_setting
-      end
-
-      RSpec.configure do |c|
-        c.custom_setting = true
-      end
-
-      describe "custom setting" do
-        it "returns the value set in the last cofigure block to get eval'd" do
-          RSpec.configuration.custom_setting.should be_true
-        end
-
-        it "is exposed as a predicate" do
-          RSpec.configuration.custom_setting?.should be_true
-        end
-      end
-      """
-    When I run `rspec ./additional_setting_spec.rb`
-    Then the examples should all pass
-