messagebus_ruby_api 0.4.7 → 0.4.8

data/spec/ruby/1.9.1/gems/rspec-expectations-2.5.0/features/custom_matchers/define_matcher_outside_rspec.feature

@@ -1,38 +0,0 @@
-Feature: define matcher outside rspec
-
-  In order to express my domain clearly in my code examples
-  As a non-rspec user
-  I want a shortcut to define custom matchers
-
-  Scenario: define a matcher with default messages
-    Given a file named "test_multiples.rb" with:
-      """
-      require "rspec/expectations"
-      require "test/unit"
-      
-      RSpec::Matchers.define :be_a_multiple_of do |expected|
-        match do |actual|
-          actual % expected == 0
-        end
-      end
-      
-      class Test::Unit::TestCase
-        include RSpec::Matchers
-      end
-      
-      class TestMultiples < Test::Unit::TestCase
-      
-        def test_9_should_be_a_multiple_of_3
-          9.should be_a_multiple_of(3)
-        end
-
-        def test_9_should_be_a_multiple_of_4
-          9.should be_a_multiple_of(4)
-        end
-        
-      end
-      """
-    When I run "ruby test_multiples.rb"
-    Then the exit status should not be 0 
-    And the output should contain "expected 9 to be a multiple of 4"
-    And the output should contain "2 tests, 0 assertions, 0 failures, 1 errors"

data/spec/ruby/1.9.1/gems/rspec-expectations-2.5.0/features/custom_matchers/define_matcher_with_fluent_interface.feature

@@ -1,24 +0,0 @@
-Feature: define matcher with fluent interface
-
-  Use the chain() method to define matchers with a fluent interface.
-  
-  Scenario: chained method with argumetn
-    Given a file named "between_spec.rb" with:
-      """
-      RSpec::Matchers.define :be_bigger_than do |first|
-        match do |actual|
-          (actual > first) && (actual < @second)
-        end
-
-        chain :but_smaller_than do |second|
-          @second = second
-        end
-      end
-
-      describe 5 do
-        it { should be_bigger_than(4).but_smaller_than(6) }
-      end
-      """
-    When I run "rspec between_spec.rb --format documentation"
-    Then the output should contain "1 example, 0 failures"
-    And  the output should contain "should be bigger than 4"

data/spec/ruby/1.9.1/gems/rspec-expectations-2.5.0/features/customized_message.feature

@@ -1,22 +0,0 @@
-Feature: customized message
-
-  RSpec tries to provide useful failure messages, but for cases in which you
-  want more specific information, you can define your own message right in the
-  example. This works for any matcher _other than the operator matchers_.
-  
-  Scenario: customize failure message
-    Given a file named "example_spec.rb" with:
-      """
-      describe Array do
-        context "when created with `new`" do
-          it "is empty" do
-            array = Array.new
-            array << 1 # trigger a failure to demonstrate the message
-            array.should be_empty, "expected empty array, got #{array.inspect}"
-          end
-        end
-      end
-
-      """
-    When I run "rspec example_spec.rb --format documentation"
-    Then the output should contain "expected empty array, got [1]"

data/spec/ruby/1.9.1/gems/rspec-expectations-2.5.0/features/diffing.feature

@@ -1,85 +0,0 @@
-Feature: diffing
-
-  When appropriate, failure messages will automatically include a diff.
-
-  Scenario: diff for a multiline string
-    Given a file named "example_spec.rb" with:
-      """
-      describe "a multiline string" do
-        it "is like another string" do
-          expected = <<-EXPECTED
-      this is the
-        expected
-          string
-      EXPECTED
-          actual = <<-ACTUAL
-      this is the
-        actual
-          string
-      ACTUAL
-          actual.should eq(expected)
-        end
-      end
-      """
-    When I run "rspec example_spec.rb"
-    Then the output should contain:
-      """
-             Diff:
-             @@ -1,4 +1,4 @@
-              this is the
-             -  expected
-             +  actual
-                  string
-      """
-
-  Scenario: diff for a multiline string and a regexp
-    Given a file named "example_spec.rb" with:
-      """
-      describe "a multiline string" do
-        it "is like another string" do
-          expected = /expected/m
-          actual = <<-ACTUAL
-      this is the
-        actual
-          string
-      ACTUAL
-          actual.should =~ expected
-        end
-      end
-      """
-    When I run "rspec example_spec.rb"
-    Then the output should contain:
-      """
-             Diff:
-             @@ -1,2 +1,4 @@
-             -/expected/m
-             +this is the
-             +  actual
-             +    string
-      """
-
-  Scenario: no diff for a single line strings
-    Given a file named "example_spec.rb" with:
-      """
-      describe "a single line string" do
-        it "is like another string" do
-          expected = "this string"
-          actual   = "that string"
-          actual.should eq(expected)
-        end
-      end
-      """
-    When I run "rspec example_spec.rb"
-    Then the output should not contain "Diff:"
-
-  Scenario: no diff for numbers
-    Given a file named "example_spec.rb" with:
-      """
-      describe "a number" do
-        it "is like another number" do
-          1.should eq(2)
-        end
-      end
-      """
-    When I run "rspec example_spec.rb"
-    Then the output should not contain "Diff:"

data/spec/ruby/1.9.1/gems/rspec-expectations-2.5.0/features/implicit_docstrings.feature

@@ -1,52 +0,0 @@
-Feature: implicit docstrings
-
-  As an RSpec user
-  I want examples to generate their own names
-  So that I can reduce duplication between example names and example code
-
-  Scenario: run passing examples
-    Given a file named "implicit_docstrings_spec.rb" with:
-    """
-    describe "Examples with no docstrings generate their own:" do
-
-      specify { 3.should be < 5 }
-
-      specify { [1,2,3].should include(2) }
-
-      specify { [1,2,3].should respond_to(:size) }
-
-    end
-    """
-
-    When I run "rspec ./implicit_docstrings_spec.rb -fdoc"
-
-    Then the output should contain "should be < 5"
-    And the output should contain "should include 2"
-    And the output should contain "should respond to #size"
-
-  Scenario: run failing examples
-    Given a file named "failing_implicit_docstrings_spec.rb" with:
-    """
-    describe "Failing examples with no descriptions" do
-
-      # description is auto-generated as "should equal(5)" based on the last #should
-      it do
-        3.should equal(2)
-        5.should equal(5)
-      end
-
-      it { 3.should be > 5 }
-
-      it { [1,2,3].should include(4) }
-
-      it { [1,2,3].should_not respond_to(:size) }
-
-    end
-    """
-
-    When I run "rspec ./failing_implicit_docstrings_spec.rb -fdoc"
-
-    Then the output should contain "should equal 2"
-    And the output should contain "should be > 5"
-    And the output should contain "should include 4"
-    And the output should contain "should not respond to #size"

data/spec/ruby/1.9.1/gems/rspec-expectations-2.5.0/features/step_definitions/additional_cli_steps.rb

@@ -1,22 +0,0 @@
-# Useful for when the output is slightly different on different versions of ruby
-Then /^the output should contain "([^"]*)" or "([^"]*)"$/ do |string1, string2|
-  unless [string1, string2].any? { |s| combined_output =~ Regexp.compile(s) }
-    fail %Q{Neither "#{string1}" or "#{string2}" were found in:\n#{combined_output}}
-  end
-end
-
-Then /^the output should contain all of these:$/ do |table|
-  table.raw.flatten.each do |string|
-    assert_partial_output(string)
-  end
-end
-
-Then /^the example(?:s)? should(?: all)? pass$/ do
-  Then %q{the output should contain "0 failures"}
-  Then %q{the exit status should be 0}
-end
-
-Then /^the example should fail$/ do
-  Then %q{the output should contain "1 failure"}
-  Then %q{the exit status should not be 0}
-end

data/spec/ruby/1.9.1/gems/rspec-expectations-2.5.0/features/support/env.rb

@@ -1 +0,0 @@
-require 'aruba'

data/spec/ruby/1.9.1/gems/rspec-expectations-2.5.0/features/test_frameworks/test_unit.feature

@@ -1,46 +0,0 @@
-Feature: Test::Unit integration
-
-  RSpec-expectations is a stand-alone gem that can be used without
-  the rest of RSpec.  It can easily be used with another test
-  framework such as Test::Unit if you like RSpec's should/should_not
-  syntax but prefer the test organization of another framework.
-
-  Scenario: Basic Test::Unit usage
-    Given a file named "rspec_expectations_test.rb" with:
-      """
-      require 'test/unit'
-      require 'rspec/expectations'
-
-      class RSpecExpectationsTest < Test::Unit::TestCase
-        RSpec::Matchers.define :be_an_integer do
-          match { |actual| Integer === actual }
-        end
-
-        def be_an_int
-          RSpec.deprecate(:be_an_int, :be_an_integer)
-          be_an_integer
-        end
-
-        def test_passing_expectation
-          x = 1 + 3
-          x.should == 4
-        end
-
-        def test_failing_expectation
-          array = [1, 2]
-          array.should be_empty
-        end
-
-        def test_expect_matcher
-          expect { @a = 5 }.to change { @a }.from(nil).to(5)
-        end
-
-        def test_custom_matcher_and_deprecation_warning
-          1.should be_an_int
-        end
-      end
-      """
-     When I run "ruby rspec_expectations_test.rb"
-     Then the output should contain "4 tests, 0 assertions, 1 failures, 0 errors" or "4 tests, 0 assertions, 0 failures, 1 errors"
-      And the output should contain "expected empty? to return true, got false"
-      And the output should contain "be_an_int is deprecated"

data/spec/ruby/1.9.1/gems/rspec-expectations-2.5.0/lib/rspec-expectations.rb

@@ -1 +0,0 @@
-require "rspec/expectations"

data/spec/ruby/1.9.1/gems/rspec-expectations-2.5.0/lib/rspec/expectations.rb

@@ -1,39 +0,0 @@
-require 'rspec/expectations/extensions'
-require 'rspec/matchers'
-require 'rspec/expectations/fail_with'
-require 'rspec/expectations/errors'
-require 'rspec/expectations/deprecation'
-require 'rspec/expectations/handler'
-require 'rspec/expectations/version'
-require 'rspec/expectations/backward_compatibility'
-require 'rspec/expectations/differ'
-
-module RSpec
-  
-  # RSpec::Expectations lets you set expectations on your objects.
-  #
-  #   result.should == 37
-  #   team.should have(11).players_on_the_field
-  #
-  # == How Expectations work.
-  #
-  # RSpec::Expectations adds two methods to Object:
-  #
-  #   should(matcher=nil)
-  #   should_not(matcher=nil)
-  #
-  # Both methods take an optional Expression Matcher (See RSpec::Matchers).
-  #
-  # When +should+ receives an Expression Matcher, it calls <tt>matches?(self)</tt>. If
-  # it returns +true+, the spec passes and execution continues. If it returns
-  # +false+, then the spec fails with the message returned by <tt>matcher.failure_message</tt>.
-  #
-  # Similarly, when +should_not+ receives a matcher, it calls <tt>matches?(self)</tt>. If
-  # it returns +false+, the spec passes and execution continues. If it returns
-  # +true+, then the spec fails with the message returned by <tt>matcher.negative_failure_message</tt>.
-  #
-  # RSpec ships with a standard set of useful matchers, and writing your own
-  # matchers is quite simple. See RSpec::Matchers for details.
-  module Expectations
-  end
-end

data/spec/ruby/1.9.1/gems/rspec-expectations-2.5.0/lib/rspec/expectations/backward_compatibility.rb

@@ -1,16 +0,0 @@
-# Cucumber 0.7 includes Rspec::Expectations
-module RSpec
-  module Expectations
-    module ConstMissing
-      def const_missing(name)
-        name == :Rspec ? RSpec : super(name)
-      end
-    end
-
-    def differ=(ignore)
-      RSpec.deprecate("RSpec::Expectations.differ=(differ)", "nothing at all (diffing is now automatic and no longer configurable)")
-    end
-  end
-end
-
-Object.extend(RSpec::Expectations::ConstMissing)

data/spec/ruby/1.9.1/gems/rspec-expectations-2.5.0/lib/rspec/expectations/deprecation.rb

@@ -1,36 +0,0 @@
-module RSpec
-
-  # This is defined in rspec-core, but we can't assume it's loaded since
-  # rspec-expectations should be usable w/o rspec-core.
-  unless respond_to?(:deprecate)
-    class << self
-      def deprecate(method, alternate_method=nil, version=nil)
-        version_string = version ? "rspec-#{version}" : "a future version of RSpec"
-
-        message = <<-NOTICE
-
-*****************************************************************
-DEPRECATION WARNING: you are using deprecated behaviour that will
-be removed from #{version_string}.
-
-#{caller(0)[2]}
-
-* #{method} is deprecated.
-NOTICE
-      if alternate_method
-        message << <<-ADDITIONAL
-* please use #{alternate_method} instead.
-ADDITIONAL
-      end
-
-        message << "*****************************************************************"
-        warn_deprecation(message)
-      end
-
-      def warn_deprecation(message)
-        send :warn, message
-      end
-    end
-  end
-end
-

data/spec/ruby/1.9.1/gems/rspec-expectations-2.5.0/lib/rspec/expectations/differ.rb

@@ -1,62 +0,0 @@
-require 'diff/lcs'
-require 'diff/lcs/hunk'
-require 'pp'
-
-module RSpec
-  module Expectations
-    class Differ
-      def initialize(ignore=nil)
-      end
-
-      # This is snagged from diff/lcs/ldiff.rb (which is a commandline tool)
-      def diff_as_string(data_new, data_old)
-        data_old = data_old.split(/\n/).map! { |e| e.chomp }
-        data_new = data_new.split(/\n/).map! { |e| e.chomp }
-        output = ""
-        diffs = Diff::LCS.diff(data_old, data_new)
-        return output if diffs.empty?
-        oldhunk = hunk = nil  
-        file_length_difference = 0
-        diffs.each do |piece|
-          begin
-            hunk = Diff::LCS::Hunk.new(
-              data_old, data_new, piece, context_lines, file_length_difference
-            )
-            file_length_difference = hunk.file_length_difference      
-            next unless oldhunk      
-            # Hunks may overlap, which is why we need to be careful when our
-            # diff includes lines of context. Otherwise, we might print
-            # redundant lines.
-            if (context_lines > 0) and hunk.overlaps?(oldhunk)
-              hunk.unshift(oldhunk)
-            else
-              output << oldhunk.diff(format)
-            end
-          ensure
-            oldhunk = hunk
-            output << "\n"
-          end
-        end  
-        #Handle the last remaining hunk
-        output << oldhunk.diff(format) << "\n"
-      end  
-
-      def diff_as_object(actual,expected)
-        actual = String === actual ? actual : PP.pp(actual,"")
-        expected = String === expected ? expected : PP.pp(expected,"")
-        diff_as_string(actual, expected)
-      end
-
-    protected
-
-      def format
-        :unified
-      end
-
-      def context_lines
-        3
-      end
-    end
-
-  end
-end