cvss-suite 1.0.8 → 1.1.0

data/vendor/cache/ruby/2.2.0/gems/rspec-its-1.2.0/LICENSE.txt

@@ -1,27 +0,0 @@
-(The MIT License)
-
-Copyright (c) 2013 Peter Alfvin
-Copyright (c) 2012 David Chelimsky, Myron Marston
-Copyright (c) 2006 David Chelimsky, The RSpec Development Team
-Copyright (c) 2005 Steven Baker
-
-MIT License
-
-Permission is hereby granted, free of charge, to any person obtaining
-a copy of this software and associated documentation files (the
-"Software"), to deal in the Software without restriction, including
-without limitation the rights to use, copy, modify, merge, publish,
-distribute, sublicense, and/or sell copies of the Software, and to
-permit persons to whom the Software is furnished to do so, subject to
-the following conditions:
-
-The above copyright notice and this permission notice shall be
-included in all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
-NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
-LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
-OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
-WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/vendor/cache/ruby/2.2.0/gems/rspec-its-1.2.0/README.md

@@ -1,72 +0,0 @@
-# RSpec::Its [![Build Status](https://travis-ci.org/rspec/rspec-its.svg)](https://travis-ci.org/rspec/rspec-its)
-
-RSpec::Its provides the `its` method as a short-hand to specify the expected value of an attribute.
-
-## Installation
-
-Add this line to your application's Gemfile:
-
-    gem 'rspec-its'
-
-And then execute:
-
-    $ bundle
-
-Or install it yourself as:
-
-    $ gem install rspec-its
-
-And require it as:
-
-    require 'rspec/its'
-
-## Usage
-
-Use the `its` method to generate a nested example group with
-a single example that specifies the expected value of an attribute of the
-subject using `should`, `should_not` or `is_expected`.
-
-`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_not eq(0) }
-
-The following expect-style method is also available:
-
-    its(:size) { is_expected.to eq(1) }
-    
-as is this alias for pluralized use:
-
-    its(:keys) { are_expected.to eq([:key1, :key2])
-    
-When the subject implements the `[]` operator, you can pass in an array with a single key to
-refer to the value returned by that operator when passed that key as an argument.
-
-    its([:key]) { is_expected.to eq(value) }
-
-For hashes, multiple keys within the array will result in successive accesses into the hash. For example:
-
-    subject { {key1: {key2: 3} } }
-    its([:key1, :key2]) { is_expected.to eq(3)
-
-For other objects, multiple keys within the array will be passed as separate arguments in a single method call to [], as in:
-
-    subject { Matrix[ [:a, :b], [:c, :d] ] }
-    its([1,1]) { should eq(:d) }
-
-Metadata arguments are supported.
-
-    its(:size, focus: true) { should eq(1) }
-
-## Contributing
-
-1. Fork it
-2. Create your feature branch (`git checkout -b my-new-feature`)
-3. Commit your changes (`git commit -am 'Add some feature'`)
-4. Push to the branch (`git push origin my-new-feature`)
-5. Create new Pull Request

data/vendor/cache/ruby/2.2.0/gems/rspec-its-1.2.0/Rakefile

@@ -1,16 +0,0 @@
-require "bundler"
-Bundler.setup
-Bundler::GemHelper.install_tasks
-
-require "rake"
-require "rspec/core/rake_task"
-
-require "cucumber/rake/task"
-Cucumber::Rake::Task.new(:cucumber)
-
-desc "Run all examples"
-RSpec::Core::RakeTask.new(:spec) do |t|
-  t.ruby_opts = %w[-w]
-end
-
-task :default => [:spec, :cucumber]

data/vendor/cache/ruby/2.2.0/gems/rspec-its-1.2.0/cucumber.yml

@@ -1,2 +0,0 @@
-default: --require features --strict --format progress --tags ~@wip features
-wip:     --require features --tags @wip:3 --wip features

data/vendor/cache/ruby/2.2.0/gems/rspec-its-1.2.0/features/its.feature

@@ -1,125 +0,0 @@
-Feature: attribute of subject
-
-  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 with the documentation option
-    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
-    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
-    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
-    Then the examples should all pass
-
- Scenario: failures are correctly reported as coming from the `its` line
-    Given a file named "example_spec.rb" with:
-      """ruby
-      describe Array do
-        context "when first created" do
-          its(:size) { should_not eq(0) }
-        end
-      end
-      """
-    When I run rspec
-    Then the output should contain "Failure/Error: its(:size) { should_not eq(0) }"
-      And the output should not match /#[^\n]*rspec[\x2f]its/
-
- Scenario: examples can be specified by exact line number
-    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 specifying line number 3
-    Then the examples should all pass
-
-  Scenario: examples can be specified by line number within containing block
-    Given a file named "example_spec.rb" with:
-    """ruby
-      describe Array do
-        context "when first created" do
-          its(:size) { should eq(0) }
-        end
-        it "should never execute this" do
-          expect(true).to be(false)
-        end
-      end
-      """
-    When I run rspec specifying line number 2
-    Then the examples should all pass

data/vendor/cache/ruby/2.2.0/gems/rspec-its-1.2.0/features/step_definitions/additional_cli_steps.rb

@@ -1,21 +0,0 @@
-When /^I run rspec( with the documentation option)?$/ do |documentation|
-  rspec_its_gem_location = File.expand_path('../../../lib/rspec/its', __FILE__)
-  require_option = "--require #{rspec_its_gem_location}"
-  format_option = documentation ? "--format documentation" : ""
-  rspec_command = ['rspec', require_option, format_option, 'example_spec.rb'].join(' ')
-  step "I run `#{rspec_command}`"
-end
-
-When /^I run rspec specifying line number (\d+)$/ do |line_number|
-  rspec_its_gem_location = File.expand_path('../../../lib/rspec/its', __FILE__)
-  require_option = "--require #{rspec_its_gem_location}"
-  file_specification = "example_spec.rb:#{line_number}"
-  rspec_command = ['rspec', require_option, file_specification].join(' ')
-  step "I run `#{rspec_command}`"
-end
-
-Then /^the example(?:s)? should(?: all)? pass$/ do
-  step %q{the output should contain "0 failures"}
-  step %q{the output should not contain "0 examples"}
-  step %q{the exit status should be 0}
-end

data/vendor/cache/ruby/2.2.0/gems/rspec-its-1.2.0/features/support/env.rb

@@ -1,23 +0,0 @@
-require 'aruba/cucumber'
-require 'rspec/core'
-require 'rspec/its'
-
-Before do
-  if RUBY_PLATFORM =~ /java/ || defined?(Rubinius)
-    @aruba_timeout_seconds = 60
-  else
-    @aruba_timeout_seconds = 10
-  end
-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'
-
-Aruba.configure do |config|
-  config.before_cmd do |cmd|
-    set_env('RBXOPT', "-Xint=true #{ENV['RBXOPT']}") # disable JIT since these processes are so short lived
-  end
-end if defined?(Rubinius)

data/vendor/cache/ruby/2.2.0/gems/rspec-its-1.2.0/lib/rspec/its.rb

@@ -1,149 +0,0 @@
-require 'rspec/its/version'
-require 'rspec/core'
-
-module RSpec
-  module Its
-
-    # Creates a nested example group named by the submitted `attribute`,
-    # and then generates an example using the submitted block.
-    #
-    # @example
-    #
-    #   # This ...
-    #   describe Array do
-    #     its(:size) { should eq(0) }
-    #   end
-    #
-    #   # ... generates the same runtime structure as this:
-    #   describe Array do
-    #     describe "size" do
-    #       it "should eq(0)" do
-    #         subject.size.should eq(0)
-    #       end
-    #     end
-    #   end
-    #
-    # The attribute can be a `Symbol` or a `String`. Given a `String`
-    # with dots, the result is as though you concatenated that `String`
-    # onto the subject in an expression.
-    #
-    # @example
-    #
-    #   describe Person do
-    #     subject do
-    #       Person.new.tap do |person|
-    #         person.phone_numbers << "555-1212"
-    #       end
-    #     end
-    #
-    #     its("phone_numbers.first") { should eq("555-1212") }
-    #   end
-    #
-    # When the subject is a `Hash`, you can refer to the Hash keys by
-    # specifying a `Symbol` or `String` in an array.
-    #
-    # @example
-    #
-    #   describe "a configuration Hash" do
-    #     subject do
-    #       { :max_users => 3,
-    #         'admin' => :all_permissions.
-    #         'john_doe' => {:permissions => [:read, :write]}}
-    #     end
-    #
-    #     its([:max_users]) { should eq(3) }
-    #     its(['admin']) { should eq(:all_permissions) }
-    #     its(['john_doe', :permissions]) { should eq([:read, :write]) }
-    #
-    #     # You can still access to its regular methods this way:
-    #     its(:keys) { should include(:max_users) }
-    #     its(:count) { should eq(2) }
-    #   end
-    #
-    # With an implicit subject, `is_expected` can be used as an alternative
-    # to `should` (e.g. for one-liner use)
-    #
-    # @example
-    #
-    #   describe Array do
-    #     its(:size) { is_expected.to eq(0) }
-    #   end
-    #
-    # You can pass more than one arguments on the `its` block to add
-    # some options to the generated example
-    #
-    # @example
-    #
-    #   # This ...
-    #   describe Array do
-    #     its(:size, :focus) { should eq(0) }
-    #   end
-    #
-    #   # ... generates the same runtime structure as this:
-    #   describe Array do
-    #     describe "size" do
-    #       it "should eq(0)", :focus do
-    #         subject.size.should eq(0)
-    #       end
-    #     end
-    #   end
-    #
-    # Note that this method does not modify `subject` in any way, so if you
-    # refer to `subject` in `let` or `before` blocks, you're still
-    # referring to the outer subject.
-    #
-    # @example
-    #
-    #   describe Person do
-    #     subject { Person.new }
-    #     before { subject.age = 25 }
-    #     its(:age) { should eq(25) }
-    #   end
-    def its(attribute, *options, &block)
-      its_caller = caller.select {|file_line| file_line !~ %r(/lib/rspec/its) }
-      describe(attribute.to_s, :caller => its_caller) do
-        let(:__its_subject) do
-          if Array === attribute
-            if Hash === subject
-              attribute.inject(subject) {|inner, attr| inner[attr] }
-            else
-              subject[*attribute]
-            end
-          else
-            attribute_chain = attribute.to_s.split('.')
-            attribute_chain.inject(subject) do |inner_subject, attr|
-              inner_subject.send(attr)
-            end
-          end
-        end
-
-        def is_expected
-          expect(__its_subject)
-        end
-        alias_method :are_expected, :is_expected
-
-        def should(matcher=nil, message=nil)
-          RSpec::Expectations::PositiveExpectationHandler.handle_matcher(__its_subject, matcher, message)
-        end
-
-        def should_not(matcher=nil, message=nil)
-          RSpec::Expectations::NegativeExpectationHandler.handle_matcher(__its_subject, matcher, message)
-        end
-
-        options << {} unless options.last.kind_of?(Hash)
-        options.last.merge!(:caller => its_caller)
-
-        example(nil, *options, &block)
-
-      end
-    end
-
-  end
-end
-
-RSpec.configure do |rspec|
-  rspec.extend RSpec::Its
-  rspec.backtrace_exclusion_patterns << %r(/lib/rspec/its)
-end
-
-RSpec::SharedContext.send(:include, RSpec::Its)

data/vendor/cache/ruby/2.2.0/gems/rspec-its-1.2.0/lib/rspec/its/version.rb

@@ -1,5 +0,0 @@
-module RSpec
-  module Its
-    VERSION = "1.2.0"
-  end
-end