messagebus_ruby_api 0.4.0 → 0.4.4

data/spec/ruby/1.9.1/gems/rspec-core-2.5.1/features/mock_framework_integration/use_any_framework.feature

@@ -0,0 +1,106 @@
+Feature: mock with an alternative framework
+
+  In addition to rspec, mocha, flexmock, and RR, you can choose an alternate
+  framework as the mocking framework. You (or the framework authors) just needs
+  to provide an adapter that hooks RSpec's events into those of the framework.
+
+  A mock framework adapter must expose three methods:
+    
+  * setup_mocks_for_rspec
+    * called before each example is run
+  * verify_mocks_for_rspec 
+    * called after each example is run
+    * this is where message expectation failures should result in an error with
+      the appropriate failure message
+  * teardown_mocks_for_rspec 
+    * called after verify_mocks_for_rspec
+    * use this to clean up resources, restore objects to earlier state, etc
+    * guaranteed to run even if there are failures
+
+  Scenario: Mock with alternate framework
+    Given a file named "expector.rb" with:
+      """
+      class Expector
+        class << self
+          def expectors
+            @expectors ||= []
+          end
+
+          def clear_expectors
+            expectors.clear
+          end
+
+          def verify_expectors
+            expectors.each {|d| d.verify}
+          end
+        end
+
+        def initialize
+          self.class.expectors << self
+        end
+
+        def expectations
+          @expectations ||= []
+        end
+
+        def expect(message)
+          expectations << message.to_s
+        end
+
+        def verify
+          unless expectations.empty?
+            raise expectations.map {|e|
+              "expected #{e}, but it was never received"
+            }.join("\n")
+          end
+        end
+
+      private
+
+        def method_missing(name, *args, &block)
+          expectations.delete(name.to_s)
+        end
+
+      public
+
+        module RSpecAdapter
+          def setup_mocks_for_rspec
+            # no setup necessary
+          end
+
+          def verify_mocks_for_rspec
+            Expector.verify_expectors.each {|d| d.verify}
+          end
+
+          def teardown_mocks_for_rspec
+            Expector.clear_expectors
+          end
+        end
+      end
+      """
+      
+    Given a file named "example_spec.rb" with:
+      """
+      require File.expand_path("../expector", __FILE__)
+
+      RSpec.configure do |config|
+        config.mock_framework = Expector::RSpecAdapter
+      end
+
+      describe Expector do
+        it "passes when message is received" do
+          expector = Expector.new
+          expector.expect(:foo)
+          expector.foo
+        end
+
+        it "fails when message is received" do
+          expector = Expector.new
+          expector.expect(:foo)
+        end
+      end
+      """
+    When I run "rspec example_spec.rb --format doc"
+    Then the exit status should be 1
+    And the output should contain "2 examples, 1 failure" 
+    And the output should contain "fails when message is received (FAILED - 1)" 

data/spec/ruby/1.9.1/gems/rspec-core-2.5.1/features/mock_framework_integration/use_flexmock.feature

@@ -0,0 +1,23 @@
+Feature: mock with flexmock
+
+  As an RSpec user who likes to mock
+  I want to be able to use flexmock
+
+  Scenario: Mock with flexmock
+    Given a file named "flexmock_example_spec.rb" with:
+      """
+      RSpec.configure do |config|
+        config.mock_framework = :flexmock
+      end
+
+      describe "plugging in flexmock" do
+        it "allows flexmock to be used" do
+          target = Object.new
+          flexmock(target).should_receive(:foo).once
+          target.foo
+        end
+      end
+      """
+    When I run "rspec ./flexmock_example_spec.rb"
+    Then the examples should all pass 
+    And the exit status should be 0

data/spec/ruby/1.9.1/gems/rspec-core-2.5.1/features/mock_framework_integration/use_mocha.feature

@@ -0,0 +1,23 @@
+Feature: mock with mocha
+
+  As an RSpec user who likes to mock
+  I want to be able to use mocha
+
+  Scenario: Mock with mocha
+    Given a file named "mocha_example_spec.rb" with:
+      """
+      RSpec.configure do |config|
+        config.mock_framework = :mocha
+      end
+
+      describe "plugging in mocha" do
+        it "allows mocha to be used" do
+          target = Object.new
+          target.expects(:foo).once
+          target.foo
+        end
+      end
+      """
+    When I run "rspec ./mocha_example_spec.rb"
+    Then the examples should all pass 
+    And the exit status should be 0

data/spec/ruby/1.9.1/gems/rspec-core-2.5.1/features/mock_framework_integration/use_rr.feature

@@ -0,0 +1,23 @@
+Feature: mock with rr
+
+  As an RSpec user who likes to mock
+  I want to be able to use rr
+
+  Scenario: Mock with rr
+    Given a file named "rr_example_spec.rb" with:
+      """
+      RSpec.configure do |config|
+        config.mock_framework = :rr
+      end
+
+      describe "plugging in rr" do
+        it "allows rr to be used" do
+          target = Object.new
+          mock(target).foo
+          target.foo
+        end
+      end
+      """
+    When I run "rspec ./rr_example_spec.rb"
+    Then the examples should all pass 
+    And the exit status should be 0

data/spec/ruby/1.9.1/gems/rspec-core-2.5.1/features/mock_framework_integration/use_rspec.feature

@@ -0,0 +1,23 @@
+Feature: mock with rspec
+
+  As an RSpec user who likes to mock
+  I want to be able to use rspec
+
+  Scenario: Mock with rspec
+    Given a file named "rspec_example_spec.rb" with:
+      """
+      RSpec.configure do |config|
+        config.mock_framework = :rspec
+      end
+
+      describe "plugging in rspec" do
+        it "allows rspec to be used" do
+          target = mock('target')
+          target.should_receive(:foo)
+          target.foo
+        end
+      end
+      """
+    When I run "rspec ./rspec_example_spec.rb"
+    Then the examples should all pass 
+    And the exit status should be 0

data/spec/ruby/1.9.1/gems/rspec-core-2.5.1/features/pending/pending_examples.feature

@@ -0,0 +1,216 @@
+Feature: pending examples
+
+  RSpec offers four ways to indicate that an example is disabled pending
+  some action.
+
+  Scenario: pending implementation
+    Given a file named "example_without_block_spec.rb" with:
+      """
+      describe "an example" do
+        it "is a pending example"
+      end
+      """
+    When I run "rspec example_without_block_spec.rb"
+    Then the exit status should be 0
+    And the output should contain "1 example, 0 failures, 1 pending"
+    And the output should contain "Not Yet Implemented"
+    And the output should contain "example_without_block_spec.rb:2"
+
+  Scenario: pending any arbitary reason, with no block
+    Given a file named "pending_without_block_spec.rb" with:
+      """
+      describe "an example" do
+        it "is implemented but waiting" do
+          pending("something else getting finished")
+          this_should_not_get_executed
+        end
+      end
+      """
+    When I run "rspec pending_without_block_spec.rb"
+    Then the exit status should be 0
+    And the output should contain "1 example, 0 failures, 1 pending"
+    And the output should contain:
+      """
+      Pending:
+        an example is implemented but waiting
+          # something else getting finished
+          # ./pending_without_block_spec.rb:2
+      """
+
+  Scenario: pending any arbitary reason, with a block that fails
+    Given a file named "pending_with_failing_block_spec.rb" with:
+      """
+      describe "an example" do
+        it "is implemented but waiting" do
+          pending("something else getting finished") do
+            raise "this is the failure"
+          end
+        end
+      end
+      """
+    When I run "rspec pending_with_failing_block_spec.rb"
+    Then the exit status should be 0
+    And the output should contain "1 example, 0 failures, 1 pending"
+    And the output should contain:
+      """
+      Pending:
+        an example is implemented but waiting
+          # something else getting finished
+          # ./pending_with_failing_block_spec.rb:2
+      """
+
+  Scenario: pending any arbitary reason, with a block that passes
+    Given a file named "pending_with_passing_block_spec.rb" with:
+      """
+      describe "an example" do
+        it "is implemented but waiting" do
+          pending("something else getting finished") do
+            true.should be(true)
+          end
+        end
+      end
+      """
+    When I run "rspec pending_with_passing_block_spec.rb"
+    Then the exit status should not be 0
+    And the output should contain "1 example, 1 failure"
+    And the output should contain "FIXED"
+    And the output should contain "Expected pending 'something else getting finished' to fail. No Error was raised."
+    And the output should contain "pending_with_passing_block_spec.rb:3"
+
+  Scenario: temporarily pending by changing "it" to "xit"
+    Given a file named "pending_with_xit_spec.rb" with:
+      """
+      describe "an example" do
+        xit "is pending using xit" do
+          true.should be(true)
+        end
+      end
+      """
+    When I run "rspec pending_with_xit_spec.rb"
+    Then the exit status should be 0
+    And the output should contain "1 example, 0 failures, 1 pending"
+    And the output should contain:
+      """
+      Pending:
+        an example is pending using xit
+      """
+
+  Scenario: example with no docstring and pending method using documentation formatter
+    Given a file named "pending_with_no_docstring_spec.rb" with:
+      """
+      describe "an example" do
+        it "checks something" do
+          (3+4).should == 7
+        end
+        specify do
+          pending
+        end
+      end
+      """
+    When I run "rspec pending_with_no_docstring_spec.rb --format documentation"
+    Then the exit status should be 0
+    And the output should contain "2 examples, 0 failures, 1 pending"
+    And the output should contain:
+      """
+      an example
+        checks something
+         (PENDING: No reason given)
+      """
+
+  Scenario: pending with no docstring using documentation formatter
+    Given a file named "pending_with_no_docstring_spec.rb" with:
+      """
+      describe "an example" do
+        it "checks something" do
+          (3+4).should == 7
+        end
+        pending do
+          "string".reverse.should == "gnirts"
+        end
+      end
+      """
+    When I run "rspec pending_with_no_docstring_spec.rb --format documentation"
+    Then the exit status should be 0
+    And the output should contain "2 examples, 0 failures, 1 pending"
+    And the output should contain:
+      """
+      an example
+        checks something
+         (PENDING: Not Yet Implemented)
+      """
+
+  Scenario: conditionally pending examples
+    Given a file named "conditionally_pending_spec.rb" with:
+      """
+      describe "a failing spec" do
+        def run_test; raise "failure"; end
+
+        it "is pending when pending with a true :if condition" do
+          pending("true :if", :if => true) { run_test }
+        end
+
+        it "fails when pending with a false :if condition" do
+          pending("false :if", :if => false) { run_test }
+        end
+
+        it "is pending when pending with a false :unless condition" do
+          pending("false :unless", :unless => false) { run_test }
+        end
+
+        it "fails when pending with a true :unless condition" do
+          pending("true :unless", :unless => true) { run_test }
+        end
+      end
+
+      describe "a passing spec" do
+        def run_test; true.should be(true); end
+
+        it "fails when pending with a true :if condition" do
+          pending("true :if", :if => true) { run_test }
+        end
+
+        it "passes when pending with a false :if condition" do
+          pending("false :if", :if => false) { run_test }
+        end
+
+        it "fails when pending with a false :unless condition" do
+          pending("false :unless", :unless => false) { run_test }
+        end
+
+        it "passes when pending with a true :unless condition" do
+          pending("true :unless", :unless => true) { run_test }
+        end
+      end
+      """
+    When I run "rspec ./conditionally_pending_spec.rb"
+    Then the output should contain "8 examples, 4 failures, 2 pending"
+    And the output should contain:
+      """
+      Pending:
+        a failing spec is pending when pending with a true :if condition
+          # true :if
+          # ./conditionally_pending_spec.rb:4
+        a failing spec is pending when pending with a false :unless condition
+          # false :unless
+          # ./conditionally_pending_spec.rb:12
+      """
+    And the output should contain:
+      """
+        1) a failing spec fails when pending with a false :if condition
+           Failure/Error: def run_test; raise "failure"; end
+      """
+    And the output should contain:
+      """
+        2) a failing spec fails when pending with a true :unless condition
+           Failure/Error: def run_test; raise "failure"; end
+      """
+    And the output should contain:
+      """
+        3) a passing spec fails when pending with a true :if condition FIXED
+           Expected pending 'true :if' to fail. No Error was raised.
+      """
+    And the output should contain:
+      """
+        4) a passing spec fails when pending with a false :unless condition FIXED
+           Expected pending 'false :unless' to fail. No Error was raised.
+      """

data/spec/ruby/1.9.1/gems/rspec-core-2.5.1/features/spec_files/arbitrary_file_suffix.feature

@@ -0,0 +1,13 @@
+Feature: arbitrary file suffix
+
+  Scenario: .spec
+    Given a file named "a.spec" with:
+      """
+      describe "something" do
+        it "does something" do
+          3.should eq(3)
+        end
+      end
+      """
+    When I run "rspec a.spec"
+    Then the examples should all pass

data/spec/ruby/1.9.1/gems/rspec-core-2.5.1/features/step_definitions/additional_cli_steps.rb

@@ -0,0 +1,20 @@
+Then /^the output should contain all of these:$/ do |table|
+  table.raw.flatten.each do |string|
+    assert_partial_output(string)
+  end
+end
+
+Then /^the output should not contain any of these:$/ do |table|
+  table.raw.flatten.each do |string|
+    combined_output.should_not =~ compile_and_escape(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 file "([^"]*)" should contain:$/ do |file, partial_content|
+  check_file_content(file, partial_content, true)
+end

data/spec/ruby/1.9.1/gems/rspec-core-2.5.1/features/subject/attribute_of_subject.feature

@@ -0,0 +1,102 @@
+Feature: attribute of subject
+
+  Use the its() method as a short-hand to generate a nested example group with
+  a single example that specifies the expected value of an attribute of the
+  subject.  This can be used with an implicit or explicit subject.
+
+  its() accepts a symbol or a string, and a block representing the example.
+
+      its(:size)    { should eq(1) }
+      its("length") { should eq(1) }
+
+  You can use a string with dots to specify a nested attribute (i.e. an
+  attribute of the attribute of the subject).
+
+      its("phone_numbers.size") { should eq(2) }
+
+  When the subject is a hash, you can pass in an array with a single key to
+  access the value at that key in the hash.
+
+      its([:key]) { should eq(value) }
+
+  Scenario: specify value of an attribute
+    Given a file named "example_spec.rb" with:
+      """
+      describe Array do
+        context "when first created" do
+          its(:size) { should eq(0) }
+        end
+      end
+      """
+    When I run "rspec example_spec.rb --format documentation"
+    Then the output should contain:
+      """
+      Array
+        when first created
+          size
+            should == 0
+      """
+
+  Scenario: specify value of a nested attribute
+    Given a file named "example_spec.rb" with:
+      """
+      class Person
+        attr_reader :phone_numbers
+        def initialize
+          @phone_numbers = []
+        end
+      end
+
+      describe Person do
+        context "with one phone number (555-1212)"do
+          subject do
+            person = Person.new
+            person.phone_numbers << "555-1212"
+            person
+          end
+
+          its("phone_numbers.first") { should eq("555-1212") }
+        end
+      end
+      """
+    When I run "rspec example_spec.rb --format documentation"
+    Then the output should contain:
+      """
+      Person
+        with one phone number (555-1212)
+          phone_numbers.first
+            should == 555-1212
+      """
+
+  Scenario: specify value of an attribute of a hash
+    Given a file named "example_spec.rb" with:
+      """
+      describe Hash do
+        context "with two items" do
+          subject do
+            {:one => 'one', :two => 'two'}
+          end
+
+          its(:size) { should eq(2) }
+        end
+      end
+      """
+    When I run "rspec example_spec.rb"
+    Then the examples should all pass
+
+  Scenario: specify value for key in a hash
+    Given a file named "example_spec.rb" with:
+      """
+      describe Hash do
+        context "with keys :one and 'two'" do
+          subject do
+            {:one => 1, "two" => 2}
+          end
+
+          its([:one]) { should eq(1) }
+          its(["two"]) { should eq(2) }
+        end
+      end
+      """
+    When I run "rspec example_spec.rb"
+    Then the examples should all pass

data/spec/ruby/1.9.1/gems/rspec-core-2.5.1/features/subject/explicit_subject.feature

@@ -0,0 +1,78 @@
+Feature: explicit subject
+
+  Use subject() in the group scope to explicitly define the value that is
+  returned by the subject() method in the example scope.
+
+  Scenario: subject in top level group
+    Given a file named "top_level_subject_spec.rb" with:
+      """
+      describe Array, "with some elements" do
+        subject { [1,2,3] }
+        it "should have the prescribed elements" do
+          subject.should == [1,2,3]
+        end
+      end
+      """
+    When I run "rspec top_level_subject_spec.rb"
+    Then the examples should all pass
+
+  Scenario: subject in a nested group
+    Given a file named "nested_subject_spec.rb" with:
+      """
+      describe Array do
+        subject { [1,2,3] }
+        describe "with some elements" do
+          it "should have the prescribed elements" do
+            subject.should == [1,2,3]
+          end
+        end
+      end
+      """
+    When I run "rspec nested_subject_spec.rb"
+    Then the examples should all pass
+
+  Scenario: access subject from before block
+    Given a file named "top_level_subject_spec.rb" with:
+      """
+      describe Array, "with some elements" do
+        subject { [] }
+        before { subject.push(1,2,3) }
+        it "should have the prescribed elements" do
+          subject.should == [1,2,3]
+        end
+      end
+      """
+    When I run "rspec top_level_subject_spec.rb"
+    Then the examples should all pass
+
+  Scenario: invoke helper method from subject block
+    Given a file named "helper_subject_spec.rb" with:
+      """
+      describe Array do
+        def prepared_array; [1,2,3] end
+        subject { prepared_array }
+        describe "with some elements" do
+          it "should have the prescribed elements" do
+            subject.should == [1,2,3]
+          end
+        end
+      end
+      """
+    When I run "rspec helper_subject_spec.rb"
+    Then the examples should all pass
+
+  Scenario: subject block is invoked at most once per example
+    Given a file named "nil_subject_spec.rb" with:
+      """
+      describe Array do
+        describe "#[]" do
+          context "with index out of bounds" do
+            before { Array.should_receive(:one_two_three).once.and_return([1,2,3]) }
+            subject { Array.one_two_three[42] }
+            it { should be_nil }
+          end
+        end
+      end
+      """
+    When I run "rspec nil_subject_spec.rb"
+    Then the examples should all pass

data/spec/ruby/1.9.1/gems/rspec-core-2.5.1/features/subject/implicit_receiver.feature

@@ -0,0 +1,29 @@
+Feature: implicit receiver
+
+  When should() is called in an example without an explicit receiver, it is
+  invoked against the subject (explicit or implicit).
+
+  Scenario: implicit subject
+    Given a file named "example_spec.rb" with:
+      """
+      describe Array do
+        describe "when first created" do
+          it { should be_empty }
+        end
+      end
+      """
+    When I run "rspec example_spec.rb"
+    Then the examples should all pass
+
+  Scenario: explicit subject
+    Given a file named "example_spec.rb" with:
+      """
+      describe Array do
+        describe "with 3 items" do
+          subject { [1,2,3] }
+          it { should_not be_empty }
+        end
+      end
+      """
+    When I run "rspec example_spec.rb"
+    Then the examples should all pass

data/spec/ruby/1.9.1/gems/rspec-core-2.5.1/features/subject/implicit_subject.feature

@@ -0,0 +1,30 @@
+Feature: implicit subject
+
+  If the first argument to the outermost example group is a class, an instance
+  of that class is exposed to each example via the subject() method.
+  
+  Scenario: subject in top level group
+    Given a file named "top_level_subject_spec.rb" with:
+      """
+      describe Array, "when first created" do
+        it "should be empty" do
+          subject.should eq([])
+        end
+      end
+      """
+    When I run "rspec ./top_level_subject_spec.rb"
+    Then the examples should all pass
+
+  Scenario: subject in a nested group
+    Given a file named "nested_subject_spec.rb" with:
+      """
+      describe Array do
+        describe "when first created" do
+          it "should be empty" do
+            subject.should eq([])
+          end
+        end
+      end
+      """
+    When I run "rspec nested_subject_spec.rb"
+    Then the examples should all pass