messagebus_ruby_api 0.4.7 → 0.4.8

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

@@ -1,74 +0,0 @@
-Feature: --tag option
-
-  Use the --tag (or -t) option to filter the examples by tags.
-  
-  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
-  an @ symbol, which 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 examples should all pass
-
-  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 examples should all pass
-
-  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 examples should all pass
-
-  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 examples should all pass
-  
-  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 examples should all pass
-  
-  Scenario: exclude examples with a simple tag
-    When I run "rspec . --tag ~skip"
-    Then the examples should all pass
-
-  Scenario: exclude examples with a simple tag and @
-    When I run "rspec . --tag ~@skip"
-    Then the examples should all pass
-    
-  Scenario: exclude examples with a name:value tag
-    When I run "rspec . --tag ~speed:slow"
-    Then the examples should all pass
-  
-  Scenario: exclude examples with a name:value tag and @
-    When I run "rspec . --tag ~@speed:slow"
-    Then the examples should all pass
-

data/spec/ruby/1.9.1/gems/rspec-core-2.5.1/features/configuration/custom_settings.feature

@@ -1,84 +0,0 @@
-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 examples should all pass
-
-  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 examples should all pass
-
-  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 examples should all pass
-

data/spec/ruby/1.9.1/gems/rspec-core-2.5.1/features/configuration/fail_fast.feature

@@ -1,77 +0,0 @@
-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 examples should all pass
-
-  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/spec/ruby/1.9.1/gems/rspec-core-2.5.1/features/configuration/read_options_from_file.feature

@@ -1,87 +0,0 @@
-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 examples should all pass
-
-  Scenario: custom options file
-    Given a file named "my.options" with:
-      """
-      --format documentation
-      """
-    And a file named "spec/example_spec.rb" with:
-      """
-      describe "formatter set in custom options file" do
-        it "sets formatter" do
-          RSpec.configuration.formatters.first.
-            should be_a(RSpec::Core::Formatters::DocumentationFormatter)
-        end
-      end
-      """
-    When I run "rspec spec/example_spec.rb --options my.options"
-    Then the examples should all pass
-
-  Scenario: RSpec ignores ./.rspec when custom options file is used
-    Given a file named "my.options" with:
-      """
-      --format documentation
-      """
-    And a file named ".rspec" with:
-      """
-      --color
-      """
-    And a file named "spec/example_spec.rb" with:
-      """
-      describe "custom options file" do
-        it "causes .rspec to be ignored" do
-          RSpec.configuration.color_enabled.should be_false
-        end
-      end
-      """
-    When I run "rspec spec/example_spec.rb --options my.options"
-    Then the examples should all pass
-
-  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.formatters.first.should be_an(RSpec::Core::Formatters::DocumentationFormatter)
-        end
-      end
-      """
-    When I run "rspec ./spec/example_spec.rb"
-    Then the examples should all pass

data/spec/ruby/1.9.1/gems/rspec-core-2.5.1/features/example_groups/basic_structure.feature

@@ -1,59 +0,0 @@
-Feature: basic structure (describe/it)
-
-  RSpec is a DSL for creating executable examples of how code is expected to
-  behave, organized in groups. It uses the words "describe" and "it" so we can
-  express concepts like a conversation:
-
-    "Describe an account when it is first opened."
-    "It has a balance of zero."
-
-  The describe() method creates a subclass of RSpec::Core::ExampleGroup. The
-  block passed to describe() is evaluated in the context of that class, so any
-  class methods of ExampleGroup are at your disposal within that block.
-
-  Within a group, you can declare nested groups using the describe() or
-  context() methods. A nested group is actually a subclass of the outer group,
-  so it has access to same methods as the outer group, as well as any class
-  methods defined in the outer group.
-
-  The it() method accepts a block, which is later executed in the context of
-  an instance of the group in which it is declared.
-
-  Scenario: one group, one example
-    Given a file named "sample_spec.rb" with:
-    """
-    describe "something" do
-      it "does something" do
-      end
-    end
-    """
-    When I run "rspec sample_spec.rb -fn"
-    Then the output should contain:
-      """
-      something
-        does something
-      """
-
-  Scenario: nested example groups (using context)
-    Given a file named "nested_example_groups_spec.rb" with:
-    """
-    describe "something" do
-      context "in one context" do
-        it "does one thing" do
-        end
-      end
-      context "in another context" do
-        it "does another thing" do
-        end
-      end
-    end
-    """
-    When I run "rspec nested_example_groups_spec.rb -fdoc"
-    Then the output should contain:
-      """
-      something
-        in one context
-          does one thing
-        in another context
-          does another thing
-      """

data/spec/ruby/1.9.1/gems/rspec-core-2.5.1/features/example_groups/shared_example_group.feature

@@ -1,177 +0,0 @@
-Feature: shared example group
-
-  Shared example groups let you describe behaviour of types or modules. When
-  declared, a shared group's content is stored. It is only realized in the
-  context of another example group, which provides any context the shared group
-  needs to run.
-
-  A shared group is included in another group using the it_behaves_like() or
-  it_should_behave_like() methods.
-
-  Scenario: shared example group applied to two groups
-    Given a file named "collection_spec.rb" with:
-    """
-    require "set"
-
-    shared_examples_for "a collection" do
-      let(:collection) { described_class.new([7, 2, 4]) }
-
-      context "initialized with 3 items" do
-        it "says it has three items" do
-          collection.size.should eq(3)
-        end
-      end
-
-      describe "#include?" do
-        context "with an an item that is in the collection" do
-          it "returns true" do
-            collection.include?(7).should be_true
-          end
-        end
-
-        context "with an an item that is not in the collection" do
-          it "returns false" do
-            collection.include?(9).should be_false
-          end
-        end
-      end
-    end
-
-    describe Array do
-      it_behaves_like "a collection"
-    end
-
-    describe Set do
-      it_behaves_like "a collection"
-    end
-    """
-    When I run "rspec collection_spec.rb --format documentation"
-    Then the examples should all pass
-    And the output should contain:
-      """
-      Array
-        behaves like a collection
-          initialized with 3 items
-            says it has three items
-          #include?
-            with an an item that is in the collection
-              returns true
-            with an an item that is not in the collection
-              returns false
-
-      Set
-        behaves like a collection
-          initialized with 3 items
-            says it has three items
-          #include?
-            with an an item that is in the collection
-              returns true
-            with an an item that is not in the collection
-              returns false
-      """
-
-  Scenario: Providing context to a shared group using a block
-    Given a file named "shared_example_group_spec.rb" with:
-    """
-    require "set"
-
-    shared_examples_for "a collection object" do
-      describe "<<" do
-        it "adds objects to the end of the collection" do
-          collection << 1
-          collection << 2
-          collection.to_a.should eq([1,2])
-        end
-      end
-    end
-
-    describe Array do
-      it_should_behave_like "a collection object" do
-        let(:collection) { Array.new }
-      end
-    end
-
-    describe Set do
-      it_should_behave_like "a collection object" do
-        let(:collection) { Set.new }
-      end
-    end
-    """
-    When I run "rspec shared_example_group_spec.rb --format documentation"
-    Then the examples should all pass
-    And the output should contain:
-      """
-      Array
-        it should behave like a collection object
-          <<
-            adds objects to the end of the collection
-
-      Set
-        it should behave like a collection object
-          <<
-            adds objects to the end of the collection
-      """
-
-  Scenario: Passing parameters to a shared example group
-    Given a file named "shared_example_group_params_spec.rb" with:
-    """
-    shared_examples_for "a measurable object" do |measurement, measurement_methods|
-      measurement_methods.each do |measurement_method|
-        it "should return #{measurement} from ##{measurement_method}" do
-          subject.send(measurement_method).should == measurement
-        end
-      end
-    end
-
-    describe Array, "with 3 items" do
-      subject { [1, 2, 3] }
-      it_should_behave_like "a measurable object", 3, [:size, :length]
-    end
-
-    describe String, "of 6 characters" do
-      subject { "FooBar" }
-      it_should_behave_like "a measurable object", 6, [:size, :length]
-    end
-    """
-    When I run "rspec shared_example_group_params_spec.rb --format documentation"
-    Then the examples should all pass
-    And the output should contain:
-      """
-      Array with 3 items
-        it should behave like a measurable object
-          should return 3 from #size
-          should return 3 from #length
-
-      String of 6 characters
-        it should behave like a measurable object
-          should return 6 from #size
-          should return 6 from #length
-      """
-
-  Scenario: Aliasing "it_should_behave_like" to "it_has_behavior"
-    Given a file named "shared_example_group_spec.rb" with:
-      """
-      RSpec.configure do |c|
-        c.alias_it_should_behave_like_to :it_has_behavior, 'has behavior:'
-      end
-
-      shared_examples_for 'sortability' do
-        it 'responds to <=>' do
-          sortable.should respond_to(:<=>)
-        end
-      end
-
-      describe String do
-        it_has_behavior 'sortability' do
-          let(:sortable) { 'sample string' }
-        end
-      end
-      """
-    When I run "rspec shared_example_group_spec.rb --format documentation"
-    Then the examples should all pass
-    And the output should contain:
-      """
-      String
-        has behavior: sortability
-          responds to <=>
-      """