vagrant-unbundled 1.9.5.1 → 1.9.7.1

data/vendor/bundle/ruby/2.4.0/gems/rspec-core-2.14.8/features/subject/attribute_of_subject.feature

@@ -1,124 +0,0 @@
-Feature: attribute of subject
-
-  WARNING: `its` will be extracted from rspec-core-3.0 into its own gem.
-
-  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:
-      """ruby
-      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 eq 0
-      """
-
-  Scenario: specify value of a nested attribute
-    Given a file named "example_spec.rb" with:
-      """ruby
-      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 eq "555-1212"
-      """
-
-  Scenario: specify value of an attribute of a hash
-    Given a file named "example_spec.rb" with:
-      """ruby
-      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:
-      """ruby
-      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
-
-  Scenario: specify value for key in a hash-like object
-    Given a file named "example_spec.rb" with:
-      """ruby
-      require 'matrix'
-
-      describe Matrix do
-        context "with values [[1, 2], [3, 4]]" do
-          subject do
-            Matrix[[1, 2], [3, 4]]
-          end
-
-          its([0, 1]) { should eq(2) }
-          its([1, 0]) { should eq(3) }
-          its([1, 2]) { should be_nil }
-        end
-      end
-      """
-    When I run `rspec example_spec.rb`
-    Then the examples should all pass

data/vendor/bundle/ruby/2.4.0/gems/rspec-core-2.14.8/features/subject/explicit_subject.feature

@@ -1,101 +0,0 @@
-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.
-
-  Note that while the examples below demonstrate how `subject` can be used as a
-  user-facing concept, we recommend that you reserve it for support of custom
-  matchers and/or extension libraries that hide its use from examples.
-
-  Scenario: subject in top level group
-    Given a file named "top_level_subject_spec.rb" with:
-      """ruby
-      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:
-      """ruby
-      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:
-      """ruby
-      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:
-      """ruby
-      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:
-      """ruby
-      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
-
-  Scenario: subject bang method
-    Given a file named "subject_bang_spec.rb" with:
-      """ruby
-      describe Array do
-        describe '#pop' do
-          let(:prepared_array) { [1,2,3] }
-          subject! { prepared_array.pop }
-          it "removes the last value from the array" do
-            prepared_array.should eq([1,2])
-          end
-          it "returns the last value of the array" do
-            subject.should eq(3)
-          end
-        end
-      end
-      """
-    When I run `rspec subject_bang_spec.rb`
-    Then the examples should all pass

data/vendor/bundle/ruby/2.4.0/gems/rspec-core-2.14.8/features/subject/implicit_receiver.feature

@@ -1,29 +0,0 @@
-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:
-      """ruby
-      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:
-      """ruby
-      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/vendor/bundle/ruby/2.4.0/gems/rspec-core-2.14.8/features/subject/implicit_subject.feature

@@ -1,63 +0,0 @@
-Feature: implicitly defined 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.
-
-  While the examples below demonstrate how `subject` can be used as a
-  user-facing concept, we recommend that you reserve it for support of custom
-  matchers and/or extension libraries that hide its use from examples.
-
-  Scenario: subject exposed in top level group
-    Given a file named "top_level_subject_spec.rb" with:
-      """ruby
-      describe Array do
-        it "should be empty when first created" do
-          subject.should be_empty
-        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:
-      """ruby
-      describe Array do
-        describe "when first created" do
-          it "should be empty" do
-            subject.should be_empty
-          end
-        end
-      end
-      """
-    When I run `rspec nested_subject_spec.rb`
-    Then the examples should all pass
-
-  Scenario: subject in a nested group with a different class (outermost wins)
-    Given a file named "nested_subject_spec.rb" with:
-      """ruby
-      class ArrayWithOneElement < Array
-        def initialize(*)
-          super
-          unshift "first element"
-        end
-      end
-
-      describe Array do
-        describe ArrayWithOneElement do
-          context "referenced as subject" do
-            it "should be empty (because it is the Array declared at the top)" do
-              subject.should be_empty
-            end
-          end
-
-          context "created in the example" do
-            it "should not be empty" do
-              ArrayWithOneElement.new.should_not be_empty
-            end
-          end
-        end
-      end
-      """
-    When I run `rspec nested_subject_spec.rb`
-    Then the examples should all pass

data/vendor/bundle/ruby/2.4.0/gems/rspec-core-2.14.8/features/support/env.rb

@@ -1,14 +0,0 @@
-require 'aruba/cucumber'
-
-timeouts = { 'java' => 60 }
-
-Before do
-  @aruba_timeout_seconds = timeouts.fetch(RUBY_PLATFORM) { 10 }
-end
-
-Aruba.configure do |config|
-  config.before_cmd do |cmd|
-    set_env('JRUBY_OPTS', "-X-C #{ENV['JRUBY_OPTS']}") # disable JIT since these processes are so short lived
-  end
-end if RUBY_PLATFORM == 'java'
-

data/vendor/bundle/ruby/2.4.0/gems/rspec-core-2.14.8/features/support/rubinius.rb

@@ -1,6 +0,0 @@
-# Required until https://github.com/rubinius/rubinius/issues/2430 is resolved
-ENV['RBXOPT'] = "#{ENV["RBXOPT"]} -Xcompiler.no_rbc"
-
-Around "@unsupported-on-rbx" do |scenario, block|
-  block.call unless defined?(Rubinius)
-end

data/vendor/bundle/ruby/2.4.0/gems/rspec-core-2.14.8/lib/autotest/discover.rb

@@ -1 +0,0 @@
-Autotest.add_discovery { "rspec2" } if File.exist?("./.rspec")

data/vendor/bundle/ruby/2.4.0/gems/rspec-core-2.14.8/lib/autotest/rspec2.rb

@@ -1,73 +0,0 @@
-require 'autotest'
-require 'rspec/core/deprecation'
-
-# Derived from the `Autotest` class, extends the `autotest` command to work
-# with RSpec.
-#
-# @note this will be extracted to a separate gem when we release rspec-3.
-class Autotest::Rspec2 < Autotest
-
-  RSPEC_EXECUTABLE = File.expand_path('../../../exe/rspec', __FILE__)
-
-  def initialize
-    super()
-    clear_mappings
-    setup_rspec_project_mappings
-
-    # Example for Ruby 1.8: http://rubular.com/r/AOXNVDrZpx
-    # Example for Ruby 1.9: http://rubular.com/r/85ag5AZ2jP
-    self.failed_results_re = /^\s*\d+\).*\n\s+(?:\e\[\d*m)?Failure.*(\n(?:\e\[\d*m)?\s+#\s(.*)?:\d+(?::.*)?(?:\e\[\d*m)?)+$/m
-    self.completed_re = /\n(?:\e\[\d*m)?\d* examples?/m
-  end
-
-  # Adds conventional spec-to-file mappings to Autotest configuation.
-  def setup_rspec_project_mappings
-    add_mapping(%r%^spec/.*_spec\.rb$%) { |filename, _|
-      filename
-    }
-    add_mapping(%r%^lib/(.*)\.rb$%) { |_, m|
-      ["spec/#{m[1]}_spec.rb"]
-    }
-    add_mapping(%r%^spec/(spec_helper|shared/.*)\.rb$%) {
-      files_matching %r%^spec/.*_spec\.rb$%
-    }
-  end
-
-  # Overrides Autotest's implementation to read rspec output
-  def consolidate_failures(failed)
-    filters = new_hash_of_arrays
-    failed.each do |spec, trace|
-      if trace =~ /(.*spec\.rb)/
-        filters[$1] << spec
-      end
-    end
-    return filters
-  end
-
-  # Overrides Autotest's implementation to generate the rspec command to run
-  def make_test_cmd(files_to_test)
-    files_to_test.empty? ? '' :
-      %|#{prefix}"#{ruby}"#{suffix} -S "#{RSPEC_EXECUTABLE}" --tty #{normalize(files_to_test).keys.flatten.map { |f| %|"#{f}"|}.join(' ')}|
-  end
-
-  # Generates a map of filenames to Arrays for Autotest
-  def normalize(files_to_test)
-    files_to_test.keys.inject({}) do |result, filename|
-      result.merge!(File.expand_path(filename) => [])
-    end
-  end
-
-  private
-
-  def suffix
-    using_bundler? ? "" : defined?(:Gem) ? " -rrubygems" : ""
-  end
-
-  def using_bundler?
-    prefix =~ /bundle exec/
-  end
-
-  def gemfile?
-    File.exist?('./Gemfile')
-  end
-end

data/vendor/bundle/ruby/2.4.0/gems/rspec-core-2.14.8/lib/rspec/autorun.rb

@@ -1,2 +0,0 @@
-require 'rspec/core'
-RSpec::Core::Runner.autorun

data/vendor/bundle/ruby/2.4.0/gems/rspec-core-2.14.8/lib/rspec/core.rb

@@ -1,169 +0,0 @@
-require_rspec = if defined?(require_relative)
-  lambda do |path|
-    require_relative path
-  end
-else
-  lambda do |path|
-    require "rspec/#{path}"
-  end
-end
-
-require 'set'
-require 'time'
-require 'rbconfig'
-require_rspec['core/filter_manager']
-require_rspec['core/dsl']
-require_rspec['core/extensions/kernel']
-require_rspec['core/extensions/instance_eval_with_args']
-require_rspec['core/extensions/module_eval_with_args']
-require_rspec['core/extensions/ordered']
-require_rspec['core/deprecation']
-require_rspec['core/backward_compatibility']
-require_rspec['core/reporter']
-
-require_rspec['core/metadata_hash_builder']
-require_rspec['core/hooks']
-require_rspec['core/memoized_helpers']
-require_rspec['core/metadata']
-require_rspec['core/pending']
-require_rspec['core/formatters']
-
-require_rspec['core/world']
-require_rspec['core/configuration']
-require_rspec['core/project_initializer']
-require_rspec['core/option_parser']
-require_rspec['core/configuration_options']
-require_rspec['core/command_line']
-require_rspec['core/runner']
-require_rspec['core/example']
-require_rspec['core/shared_example_group/collection']
-require_rspec['core/shared_example_group']
-require_rspec['core/example_group']
-require_rspec['core/version']
-
-module RSpec
-  autoload :SharedContext, 'rspec/core/shared_context'
-
-  # @private
-  def self.wants_to_quit
-  # Used internally to determine what to do when a SIGINT is received
-    world.wants_to_quit
-  end
-
-  # @private
-  # Used internally to determine what to do when a SIGINT is received
-  def self.wants_to_quit=(maybe)
-    world.wants_to_quit=(maybe)
-  end
-
-  # @private
-  # Internal container for global non-configuration data
-  def self.world
-    @world ||= RSpec::Core::World.new
-  end
-
-  # @private
-  # Used internally to set the global object
-  def self.world=(new_world)
-    @world = new_world
-  end
-
-  # @private
-  # Used internally to ensure examples get reloaded between multiple runs in
-  # the same process.
-  def self.reset
-    @world = nil
-    @configuration = nil
-  end
-
-  # Returns the global [Configuration](RSpec/Core/Configuration) object. While you
-  # _can_ use this method to access the configuration, the more common
-  # convention is to use [RSpec.configure](RSpec#configure-class_method).
-  #
-  # @example
-  #     RSpec.configuration.drb_port = 1234
-  # @see RSpec.configure
-  # @see Core::Configuration
-  def self.configuration
-    if block_given?
-      RSpec.warn_deprecation <<-WARNING
-
-*****************************************************************
-DEPRECATION WARNING
-
-* RSpec.configuration with a block is deprecated and has no effect.
-* please use RSpec.configure with a block instead.
-
-Called from #{caller(0)[1]}
-*****************************************************************
-
-WARNING
-    end
-    @configuration ||= RSpec::Core::Configuration.new
-  end
-
-  # @private
-  # Used internally to set the global object
-  def self.configuration=(new_configuration)
-    @configuration = new_configuration
-  end
-
-  # Yields the global configuration to a block.
-  # @yield [Configuration] global configuration
-  #
-  # @example
-  #     RSpec.configure do |config|
-  #       config.add_formatter 'documentation'
-  #     end
-  # @see Core::Configuration
-  def self.configure
-    yield configuration if block_given?
-  end
-
-  # @private
-  # Used internally to clear remaining groups when fail_fast is set
-  def self.clear_remaining_example_groups
-    world.example_groups.clear
-  end
-
-  # @private
-  def self.windows_os?
-    RbConfig::CONFIG['host_os'] =~ /cygwin|mswin|mingw|bccwin|wince|emx/
-  end
-
-  module Core
-    # @private
-    # This avoids issues with reporting time caused by examples that
-    # change the value/meaning of Time.now without properly restoring
-    # it.
-    class Time
-      class << self
-        define_method(:now,&::Time.method(:now))
-      end
-    end
-  end
-
-  MODULES_TO_AUTOLOAD = {
-    :Matchers     => "rspec/expectations",
-    :Expectations => "rspec/expectations",
-    :Mocks        => "rspec/mocks"
-  }
-
-  def self.const_missing(name)
-    # Load rspec-expectations when RSpec::Matchers is referenced. This allows
-    # people to define custom matchers (using `RSpec::Matchers.define`) before
-    # rspec-core has loaded rspec-expectations (since it delays the loading of
-    # it to allow users to configure a different assertion/expectation
-    # framework). `autoload` can't be used since it works with ruby's built-in
-    # require (e.g. for files that are available relative to a load path dir),
-    # but not with rubygems' extended require.
-    #
-    # As of rspec 2.14.1, we no longer require `rspec/mocks` and
-    # `rspec/expectations` when `rspec` is required, so we want
-    # to make them available as an autoload. For more info, see:
-    require MODULES_TO_AUTOLOAD.fetch(name) { return super }
-    ::RSpec.const_get(name)
-  end
-end
-
-require_rspec['core/backward_compatibility']