messagebus_ruby_api 0.4.7 → 0.4.8

data/spec/ruby/1.9.1/gems/rspec-core-2.5.1/features/command_line/README.md

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

data/spec/ruby/1.9.1/gems/rspec-core-2.5.1/features/command_line/configure.feature

@@ -1,22 +0,0 @@
-Feature: --configure option
-
-  Use the --configure option on the command line to generate configuration
-  files.
-
-  The only supported argument, so far, is "autotest", which creates a .rspec
-  file in your project root directory. When autotest sees this file, it knows
-  to load RSpec's Autotest subclass.
-
-  Scenario: generate .rspec file for autotest
-    When I run "rspec --configure autotest"
-    Then the following files should exist:
-      | .rspec |
-    And the output should contain ".rspec file did not exist, so it was created."
-
-  Scenario: .rspec file already exists
-    Given a file named ".rspec" with:
-      """
-      --color
-      """
-    When I run "rspec --configure autotest"
-    Then the output should contain ".rspec file already exists, so nothing was changed."

data/spec/ruby/1.9.1/gems/rspec-core-2.5.1/features/command_line/example_name_option.feature

@@ -1,86 +0,0 @@
-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/spec/ruby/1.9.1/gems/rspec-core-2.5.1/features/command_line/exit_status.feature

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

data/spec/ruby/1.9.1/gems/rspec-core-2.5.1/features/command_line/format_option.feature

@@ -1,73 +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
-
-  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/spec/ruby/1.9.1/gems/rspec-core-2.5.1/features/command_line/line_number_appended_to_path.feature

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

data/spec/ruby/1.9.1/gems/rspec-core-2.5.1/features/command_line/line_number_option.feature

@@ -1,45 +0,0 @@
-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
-
-  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_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"
-
-  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/spec/ruby/1.9.1/gems/rspec-core-2.5.1/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 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
-      
-