vim-jar 0.0.1

data/bundler/ruby/1.8/gems/rspec-core-2.1.0/features/command_line/example_name_option.feature

@@ -0,0 +1,86 @@
+Feature: example name option
+
+  Use the --example (or -e) option to filter the examples to be run by name.
+
+  The argument is compiled to a Ruby Regexp, and matched against the full
+  description of the example, which is the concatenation of descriptions of the
+  group (including any nested groups) and the example.
+
+  This allows you to run a single uniquely named example, all examples with
+  similar names, all the example in a uniquely named group, etc, etc.
+
+  Background:
+    Given a file named "first_spec.rb" with:
+      """
+      describe "first group" do
+        it "first example in first group" do; end
+        it "second example in first group" do; end
+      end
+      """
+    And a file named "second_spec.rb" with:
+      """
+      describe "second group" do
+        it "first example in second group" do; end
+        it "second example in second group" do; end
+      end
+      """
+    And a file named "third_spec.rb" with:
+      """
+      describe "third group" do
+        it "first example in third group" do; end
+        context "nested group" do
+          it "first example in nested group" do; end
+          it "second example in nested group" do; end
+        end
+      end
+      """
+    And a file named "fourth_spec.rb" with:
+      """
+      describe Array do
+        describe "#length" do
+          it "is the number of items" do
+            Array.new([1,2,3]).length.should eq 3
+          end
+        end
+      end
+      """
+
+  Scenario: no matches
+    When I run "rspec . --example nothing_like_this"
+    Then the output should contain "0 examples, 0 failures"
+
+  Scenario: match on one word
+    When I run "rspec . --example example"
+    Then the output should contain "7 examples, 0 failures"
+
+  Scenario: one match in each context
+    When I run "rspec . --example 'first example'"
+    Then the output should contain "4 examples, 0 failures"
+
+  Scenario: one match in one file using just the example name
+    When I run "rspec . --example 'first example in first group'"
+    Then the output should contain "1 example, 0 failures"
+
+  Scenario: one match in one file using the example name and the group name
+    When I run "rspec . --example 'first group first example in first group'"
+    Then the output should contain "1 example, 0 failures"
+
+  Scenario: one match in one file using regexp
+    When I run "rspec . --example 'first .* first example'"
+    Then the output should contain "1 example, 0 failures"
+
+  Scenario: all examples in one group
+    When I run "rspec . --example 'first group'"
+    Then the output should contain "2 examples, 0 failures"
+
+  Scenario: one match in one file with group name
+    When I run "rspec . --example 'second group first example'"
+    Then the output should contain "1 example, 0 failures"
+
+  Scenario: all examples in one group including examples in nested groups
+    When I run "rspec . --example 'third group'"
+    Then the output should contain "3 examples, 0 failures"
+
+  Scenario: Object#method
+    When I run "rspec . --example 'Array#length'"
+    Then the output should contain "1 example, 0 failures"

data/bundler/ruby/1.8/gems/rspec-core-2.1.0/features/command_line/exit_status.feature

@@ -0,0 +1,52 @@
+Feature: exit status
+
+  In order to fail the build when it should, the spec CLI exits with an
+  appropriate exit status
+
+  Scenario: exit with 0 when all examples pass
+    Given a file named "ok_spec.rb" with:
+      """
+      describe "ok" do
+        it "passes" do
+        end
+      end
+      """
+    When I run "rspec ok_spec.rb"
+    Then the exit status should be 0
+    And the stdout should contain "1 example, 0 failures"
+
+  Scenario: exit with 1 when one example fails
+    Given a file named "ko_spec.rb" with:
+      """
+      describe "KO" do
+        it "fails" do
+          raise "KO"
+        end
+      end
+      """
+    When I run "rspec ko_spec.rb"
+    Then the exit status should be 1
+    And the stdout should contain "1 example, 1 failure"
+
+  Scenario: exit with 1 when a nested examples fails
+    Given a file named "nested_ko_spec.rb" with:
+      """
+      describe "KO" do
+        describe "nested" do
+          it "fails" do
+            raise "KO"
+          end
+        end
+      end
+      """
+    When I run "rspec nested_ko_spec.rb"
+    Then the exit status should be 1
+    And the stdout should contain "1 example, 1 failure"
+      
+  Scenario: exit with 0 when no examples are run
+    Given a file named "a_no_examples_spec.rb" with:
+      """
+      """
+    When I run "rspec a_no_examples_spec.rb"
+    Then the exit status should be 0
+    And the stdout should contain "0 examples, 0 failures"

data/bundler/ruby/1.8/gems/rspec-core-2.1.0/features/command_line/line_number_appended_to_path.feature

@@ -0,0 +1,106 @@
+Feature: line number appended to file path
+
+  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:
+      """
+      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
+      """
+
+  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"
+    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"
+    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"
+    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"
+    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"
+    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"
+    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"
+    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"
+    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"
+    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"
+    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"
+    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/bundler/ruby/1.8/gems/rspec-core-2.1.0/features/command_line/line_number_option.feature

@@ -0,0 +1,45 @@
+Feature: line number option
+
+  To run a single example or group, you can use the --line option:
+
+    rspec path/to/example_spec.rb --line 37
+
+  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
+        
+      end
+      """
+    When I run "rspec example_spec.rb --line 5 --format doc"
+    Then the output should contain "1 example, 0 failures"
+    Then the output should contain "should be > 8"
+    But the stdout should not contain "should be < 10"
+
+  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 5 --format doc"
+    Then the output should contain "1 example, 0 failures"
+    Then the output should contain "should be > 8"
+    But the stdout should not contain "should be < 10"

data/bundler/ruby/1.8/gems/rspec-core-2.1.0/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/bundler/ruby/1.8/gems/rspec-core-2.1.0/features/command_line/tag.feature

@@ -0,0 +1,74 @@
+Feature: tag option
+
+  Use the --tag (or -t) option to filter the examples to be run by tag.
+  
+  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
+  a @, that 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", :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 output should contain "0 examples, 0 failures"
+
+  Scenario: filter examples with a simple tag
+    When I run "rspec . --tag focus"
+    Then the output should contain "Run filtered using {:focus=>true}"
+    And the output should contain "1 example, 0 failures"
+
+  Scenario: filter examples with a simple tag and @
+    When I run "rspec . --tag @focus"
+    Then the output should contain "Run filtered using {:focus=>true}"
+    Then the output should contain "1 example, 0 failures"
+
+  Scenario: filter examples with a name:value tag
+    When I run "rspec . --tag type:special"
+    Then the output should contain:
+      """
+      Run filtered using {:type=>"special"}
+      """
+    And the output should contain "1 example, 0 failures"
+  
+  Scenario: filter examples with a name:value tag and @
+    When I run "rspec . --tag @type:special"
+    Then the output should contain:
+      """
+      Run filtered using {:type=>"special"}
+      """
+    And the output should contain "1 example, 0 failures"
+  
+  Scenario: exclude examples with a simple tag
+    When I run "rspec . --tag ~skip"
+    Then the output should contain "4 examples, 0 failures"
+
+  Scenario: exclude examples with a simple tag and @
+    When I run "rspec . --tag ~@skip"
+    Then the output should contain "4 examples, 0 failures"
+    
+  Scenario: exclude examples with a name:value tag
+    When I run "rspec . --tag ~speed:slow"
+    Then the output should contain "4 examples, 0 failures"
+  
+  Scenario: exclude examples with a name:value tag and @
+    When I run "rspec . --tag ~@speed:slow"
+    Then the output should contain "4 examples, 0 failures"
+

data/bundler/ruby/1.8/gems/rspec-core-2.1.0/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 output should contain "0 failures"
+
+  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 output should contain "0 failures"
+
+  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 output should contain "0 failures"
+

data/bundler/ruby/1.8/gems/rspec-core-2.1.0/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 output should contain "2 examples, 0 failures"
+
+  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/bundler/ruby/1.8/gems/rspec-core-2.1.0/features/configuration/read_options_from_file.feature

@@ -0,0 +1,74 @@
+Feature: read command line configuration options from files
+
+  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.
+  
+  Scenario: color set in .rspec
+    Given a file named ".rspec" with:
+      """
+      --color
+      """
+    And a file named "spec/example_spec.rb" with:
+      """
+      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"
+
+  Scenario: formatter set in RSpec.configure overrides .rspec
+    Given a file named ".rspec" with:
+      """
+      --format progress
+      """
+    And a file named "spec/spec_helper.rb" with:
+      """
+      RSpec.configure {|c| c.formatter = 'documentation'}
+      """
+    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
+        end
+      end
+      """
+    When I run "rspec ./spec/example_spec.rb"
+    Then the output should contain "1 example, 0 failures"
+    
+  Scenario: using ERB in .rspec
+    Given a file named ".rspec" with:
+      """
+      --format <%= true ? 'documentation' : 'progress' %>
+      """
+    And a file named "spec/example_spec.rb" with:
+      """
+      describe "formatter" do
+        it "is set to documentation" do
+          RSpec.configuration.formatter.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"