horseman 0.0.2 → 0.0.3

data/vendor/ruby/1.9.1/gems/rspec-core-2.8.0/features/command_line/README.md

@@ -0,0 +1,28 @@
+The `rspec` command comes with several options you can use to customize RSpec's
+behavior, including output formats, filtering examples, etc.
+
+For a full list of options, run the `rspec` command with the `--help` flag:
+
+    $ rspec --help
+
+### Run with `ruby`
+
+Generally, life is simpler if you just use the `rspec` command. If you must use the `ruby`
+command, however, you'll want to do the following:
+
+* `require 'rspec/autorun'`
+
+This tells RSpec to run your examples.  Do this in any file that you are
+passing to the `ruby` command.
+
+* Update the `LOAD_PATH`
+
+It is conventional to put configuration in and require assorted support files
+from `spec/spec_helper.rb`. It is also conventional to require that file from
+the spec files using `require 'spec_helper'`. This works because RSpec
+implicitly adds the `spec` directory to the `LOAD_PATH`. It also adds `lib`, so
+your implementation files will be on the `LOAD_PATH` as well.
+
+If you're using the `ruby` command, you'll need to do this yourself:
+
+    ruby -Ilib -Ispec path/to/spec.rb

data/vendor/ruby/1.9.1/gems/rspec-core-2.8.0/features/command_line/example_name_option.feature

@@ -0,0 +1,86 @@
+Feature: --example option
+
+  Use the --example (or -e) option to filter examples 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 examples 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 examples should all pass
+
+  Scenario: match on one word
+    When I run `rspec . --example example`
+    Then the examples should all pass
+
+  Scenario: one match in each context
+    When I run `rspec . --example 'first example'`
+    Then the examples should all pass
+
+  Scenario: one match in one file using just the example name
+    When I run `rspec . --example 'first example in first group'`
+    Then the examples should all pass
+
+  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 examples should all pass
+
+  Scenario: one match in one file using regexp
+    When I run `rspec . --example 'first .* first example'`
+    Then the examples should all pass
+
+  Scenario: all examples in one group
+    When I run `rspec . --example 'first group'`
+    Then the examples should all pass
+
+  Scenario: one match in one file with group name
+    When I run `rspec . --example 'second group first example'`
+    Then the examples should all pass
+
+  Scenario: all examples in one group including examples in nested groups
+    When I run `rspec . --example 'third group'`
+    Then the examples should all pass
+
+  Scenario: Object#method
+    When I run `rspec . --example 'Array#length'`
+    Then the examples should all pass

data/vendor/ruby/1.9.1/gems/rspec-core-2.8.0/features/command_line/exit_status.feature

@@ -0,0 +1,83 @@
+Feature: exit status
+
+  The rspec command exits with an exit status of 0 if all examples pass,
+  and 1 if any examples fail. The failure exit code can be overridden
+  using the --failure-exit-code option.
+
+  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 examples should all pass
+
+  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 output 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 output 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 output should contain "0 examples"
+
+  Scenario: exit with 2 when one example fails and --failure-exit-code is 2
+    Given a file named "ko_spec.rb" with:
+      """
+      describe "KO" do
+        it "fails" do
+          raise "KO"
+        end
+      end
+      """
+    When I run `rspec --failure-exit-code 2 ko_spec.rb`
+    Then the exit status should be 2
+    And the output should contain "1 example, 1 failure"
+
+  @wip
+  Scenario: exit with rspec's exit code when an at_exit hook is added upstream
+    Given a file named "exit_at_spec.rb" with:
+      """
+      require 'rspec/autorun'
+
+      describe "exit 0 at_exit" do
+        it "does not interfere with rspec's exit code" do
+          at_exit { exit 0 }
+          fail
+        end
+      end
+      """
+    When I run `rspec exit_at_spec.rb`
+    Then the exit status should be 1
+    And the output should contain "1 example, 1 failure"

data/vendor/ruby/1.9.1/gems/rspec-core-2.8.0/features/command_line/format_option.feature

@@ -0,0 +1,81 @@
+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 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/vendor/ruby/1.9.1/gems/rspec-core-2.8.0/features/command_line/init.feature

@@ -0,0 +1,18 @@
+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/vendor/ruby/1.9.1/gems/rspec-core-2.8.0/features/command_line/line_number_appended_to_path.feature

@@ -0,0 +1,140 @@
+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/vendor/ruby/1.9.1/gems/rspec-core-2.8.0/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/vendor/ruby/1.9.1/gems/rspec-core-2.8.0/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/vendor/ruby/1.9.1/gems/rspec-core-2.8.0/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/vendor/ruby/1.9.1/gems/rspec-core-2.8.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 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/vendor/ruby/1.9.1/gems/rspec-core-2.8.0/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"