gem_repackager 0.1.0

data/support/gems/rspec-core-2.11.1/features/command_line/line_number_option.feature

@@ -0,0 +1,58 @@
+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/support/gems/rspec-core-2.11.1/features/command_line/order.feature

@@ -0,0 +1,29 @@
+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/support/gems/rspec-core-2.11.1/features/command_line/pattern_option.feature

@@ -0,0 +1,31 @@
+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/support/gems/rspec-core-2.11.1/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 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/support/gems/rspec-core-2.11.1/features/command_line/ruby.feature

@@ -0,0 +1,22 @@
+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/support/gems/rspec-core-2.11.1/features/command_line/tag.feature

@@ -0,0 +1,91 @@
+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/support/gems/rspec-core-2.11.1/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/support/gems/rspec-core-2.11.1/features/configuration/custom_settings.feature

@@ -0,0 +1,84 @@
+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
+

data/support/gems/rspec-core-2.11.1/features/configuration/default_path.feature

@@ -0,0 +1,38 @@
+Feature: default_path
+
+  As of rspec-2.7, you can just type `rspec` to run all specs that live
+  in the `spec` directory.
+
+  This is supported by a `--default_path` option, which is set to `spec` by
+  default. If you prefer to keep your specs in a different directory, or assign
+  an individual file to `--default_path`, you can do so on the command line or
+  in a configuration file (`.rspec`, `~/.rspec`, or a custom file).
+
+  NOTE: this option is not supported on `RSpec.configuration`, as it needs to
+  be set before spec files are loaded.
+
+  Scenario: run `rspec` with default default_path (`spec` directory)
+    Given a file named "spec/example_spec.rb" with:
+      """
+      describe "an example" do
+        it "passes" do
+        end
+      end
+      """
+    When I run `rspec`
+    Then the output should contain "1 example, 0 failures"
+    
+  Scenario: run `rspec` with customized default_path
+    Given a file named ".rspec" with:
+      """
+      --default_path behavior
+      """
+    Given a file named "behavior/example_spec.rb" with:
+      """      
+      describe "an example" do
+        it "passes" do
+        end
+      end
+      """
+    When I run `rspec`
+    Then the output should contain "1 example, 0 failures"