Gemfile.lock

PATH
  remote: .
  specs:
    survey-gizmo-ruby (6.4.0)
      activesupport (>= 3.0, < 5.1)
      addressable (~> 2)
      awesome_print (~> 1)
      faraday (~> 0.9, >= 0.9.1)
      faraday_middleware (~> 0.9)
      i18n
      retriable (>= 2.0, < 4.0)
      virtus (>= 1.0.0)

GEM
  remote: https://rubygems.org/
  specs:
    activesupport (5.0.1)
      concurrent-ruby (~> 1.0, >= 1.0.2)
      i18n (~> 0.7)
      minitest (~> 5.1)
      tzinfo (~> 1.1)
    addressable (2.5.0)
      public_suffix (~> 2.0, >= 2.0.2)
    awesome_print (1.7.0)
    axiom-types (0.1.1)
      descendants_tracker (~> 0.0.4)
      ice_nine (~> 0.11.0)
      thread_safe (~> 0.3, >= 0.3.1)
    coercible (1.0.0)
      descendants_tracker (~> 0.0.1)
    concurrent-ruby (1.0.5)
    crack (0.4.3)
      safe_yaml (~> 1.0.0)
    descendants_tracker (0.0.4)
      thread_safe (~> 0.3, >= 0.3.1)
    diff-lcs (1.3)
    equalizer (0.0.11)
    faraday (0.11.0)
      multipart-post (>= 1.2, < 3)
    faraday_middleware (0.11.0.1)
      faraday (>= 0.7.4, < 1.0)
    hashdiff (0.3.2)
    i18n (0.8.1)
    ice_nine (0.11.2)
    minitest (5.10.1)
    multipart-post (2.0.0)
    public_suffix (2.0.5)
    rake (12.0.0)
    retriable (3.0.1)
    rspec (3.4.0)
      rspec-core (~> 3.4.0)
      rspec-expectations (~> 3.4.0)
      rspec-mocks (~> 3.4.0)
    rspec-core (3.4.4)
      rspec-support (~> 3.4.0)
    rspec-expectations (3.4.0)
      diff-lcs (>= 1.2.0, < 2.0)
      rspec-support (~> 3.4.0)
    rspec-mocks (3.4.1)
      diff-lcs (>= 1.2.0, < 2.0)
      rspec-support (~> 3.4.0)
    rspec-support (3.4.1)
    safe_yaml (1.0.4)
    thread_safe (0.3.6)
    tzinfo (1.2.2)
      thread_safe (~> 0.1)
    virtus (1.0.5)
      axiom-types (~> 0.1)
      coercible (~> 1.0)
      descendants_tracker (~> 0.0, >= 0.0.3)
      equalizer (~> 0.0, >= 0.0.9)
    webmock (2.3.2)
      addressable (>= 2.3.6)
      crack (>= 0.3.2)
      hashdiff
    yard (0.9.8)

PLATFORMS
  ruby

DEPENDENCIES
  rake (~> 12.0.0)
  rspec (~> 3.4.0)
  survey-gizmo-ruby!
  webmock
  yard

BUNDLED WITH
   1.14.5

rspec output

/Users/jeremy.mcnevin/.rvm/rubies/ruby-2.3.1/bin/ruby -I/Users/jeremy.mcnevin/.rvm/gems/ruby-2.3.1/gems/rspec-support-3.4.1/lib:/Users/jeremy.mcnevin/.rvm/gems/ruby-2.3.1/gems/rspec-core-3.4.4/lib /Users/jeremy.mcnevin/.rvm/gems/ruby-2.3.1/gems/rspec-core-3.4.4/exe/rspec spec/configuration_spec.rb spec/logger_spec.rb spec/resource_spec.rb
....WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Actual error raised was #<NoMethodError: undefined method `[]' for nil:NilClass>. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /Users/jeremy.mcnevin/Source/survey-gizmo-ruby/spec/configuration_spec.rb:54:in `block (3 levels) in <top (required)>'.
...........WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Actual error raised was #<SurveyGizmo::BadResponseError: something is wrong>. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /Users/jeremy.mcnevin/Source/survey-gizmo-ruby/spec/support/spec_shared_api_object.rb:33:in `block (3 levels) in <top (required)>'.
..WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Actual error raised was #<RuntimeError: No id; can't delete #<SurveyGizmoSpec::ResourceTest:70243113192800>
  "title" => "Spec"
  "test_id" => "5"
!>. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /Users/jeremy.mcnevin/Source/survey-gizmo-ruby/spec/support/spec_shared_api_object.rb:50:in `block (3 levels) in <top (required)>'.
......WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Actual error raised was #<SurveyGizmo::BadResponseError: There was an error!>. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /Users/jeremy.mcnevin/Source/survey-gizmo-ruby/spec/support/spec_shared_object_with_errors.rb:8:in `block (3 levels) in <top (required)>'.
WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Actual error raised was #<SurveyGizmo::BadResponseError: There was an error!>. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /Users/jeremy.mcnevin/Source/survey-gizmo-ruby/spec/support/spec_shared_object_with_errors.rb:9:in `block (3 levels) in <top (required)>'.
.........WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Actual error raised was #<SurveyGizmo::BadResponseError: something is wrong>. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /Users/jeremy.mcnevin/Source/survey-gizmo-ruby/spec/support/spec_shared_api_object.rb:33:in `block (3 levels) in <top (required)>'.
..WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Actual error raised was #<RuntimeError: No id; can't delete #<SurveyGizmo::API::Survey:70243105200600>
  "team" => "[]"
  "type" => "survey"
  "status" => "In Design"
  "title" => "Spec"
  "title_ml" => "{}"
  "links" => "{}"
  "languages" => "[]"
  "statistics" => "[]"
!>. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /Users/jeremy.mcnevin/Source/survey-gizmo-ruby/spec/support/spec_shared_api_object.rb:50:in `block (3 levels) in <top (required)>'.
......WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Actual error raised was #<SurveyGizmo::BadResponseError: There was an error!>. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /Users/jeremy.mcnevin/Source/survey-gizmo-ruby/spec/support/spec_shared_object_with_errors.rb:8:in `block (3 levels) in <top (required)>'.
WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Actual error raised was #<SurveyGizmo::BadResponseError: There was an error!>. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /Users/jeremy.mcnevin/Source/survey-gizmo-ruby/spec/support/spec_shared_object_with_errors.rb:9:in `block (3 levels) in <top (required)>'.
........WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Actual error raised was #<SurveyGizmo::BadResponseError: something is wrong>. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /Users/jeremy.mcnevin/Source/survey-gizmo-ruby/spec/support/spec_shared_api_object.rb:33:in `block (3 levels) in <top (required)>'.
..WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Actual error raised was #<RuntimeError: No id; can't delete #<SurveyGizmo::API::Question:70243100851060>
  "title" => "Spec Question"
  "type" => "radio"
  "properties" => "{}"
  "options" => "[]"
  "survey_id" => "1234"
  "page_id" => "1"
  "sub_question_skus" => "[]"
!>. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /Users/jeremy.mcnevin/Source/survey-gizmo-ruby/spec/support/spec_shared_api_object.rb:50:in `block (3 levels) in <top (required)>'.
......WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Actual error raised was #<SurveyGizmo::BadResponseError: There was an error!>. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /Users/jeremy.mcnevin/Source/survey-gizmo-ruby/spec/support/spec_shared_object_with_errors.rb:8:in `block (3 levels) in <top (required)>'.
WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Actual error raised was #<SurveyGizmo::BadResponseError: There was an error!>. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /Users/jeremy.mcnevin/Source/survey-gizmo-ruby/spec/support/spec_shared_object_with_errors.rb:9:in `block (3 levels) in <top (required)>'.
..........WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Actual error raised was #<SurveyGizmo::BadResponseError: something is wrong>. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /Users/jeremy.mcnevin/Source/survey-gizmo-ruby/spec/support/spec_shared_api_object.rb:33:in `block (3 levels) in <top (required)>'.
..WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Actual error raised was #<RuntimeError: No id; can't delete #<SurveyGizmo::API::Option:70243103090260>
  "title" => "Spec Question"
  "survey_id" => "1234"
  "page_id" => "1"
  "question_id" => "1"
  "value" => "Spec Answer"
  "properties" => "{}"
!>. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /Users/jeremy.mcnevin/Source/survey-gizmo-ruby/spec/support/spec_shared_api_object.rb:50:in `block (3 levels) in <top (required)>'.
......WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Actual error raised was #<SurveyGizmo::BadResponseError: There was an error!>. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /Users/jeremy.mcnevin/Source/survey-gizmo-ruby/spec/support/spec_shared_object_with_errors.rb:8:in `block (3 levels) in <top (required)>'.
WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Actual error raised was #<SurveyGizmo::BadResponseError: There was an error!>. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /Users/jeremy.mcnevin/Source/survey-gizmo-ruby/spec/support/spec_shared_object_with_errors.rb:9:in `block (3 levels) in <top (required)>'.
.....WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Actual error raised was #<SurveyGizmo::BadResponseError: something is wrong>. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /Users/jeremy.mcnevin/Source/survey-gizmo-ruby/spec/support/spec_shared_api_object.rb:33:in `block (3 levels) in <top (required)>'.
..WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Actual error raised was #<RuntimeError: No id; can't delete #<SurveyGizmo::API::Page:70243114013260>
  "title" => "Spec Page"
  "properties" => "{}"
  "survey_id" => "1234"
  "questions" => "[]"
!>. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /Users/jeremy.mcnevin/Source/survey-gizmo-ruby/spec/support/spec_shared_api_object.rb:50:in `block (3 levels) in <top (required)>'.
......WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Actual error raised was #<SurveyGizmo::BadResponseError: There was an error!>. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /Users/jeremy.mcnevin/Source/survey-gizmo-ruby/spec/support/spec_shared_object_with_errors.rb:8:in `block (3 levels) in <top (required)>'.
WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Actual error raised was #<SurveyGizmo::BadResponseError: There was an error!>. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /Users/jeremy.mcnevin/Source/survey-gizmo-ruby/spec/support/spec_shared_object_with_errors.rb:9:in `block (3 levels) in <top (required)>'.
.....WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Actual error raised was #<SurveyGizmo::BadResponseError: something is wrong>. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /Users/jeremy.mcnevin/Source/survey-gizmo-ruby/spec/support/spec_shared_api_object.rb:33:in `block (3 levels) in <top (required)>'.
..WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Actual error raised was #<RuntimeError: No id; can't delete #<SurveyGizmo::API::Response:70243101778780>
  "survey_id" => "1234"
  "variable" => "{}"
  "meta" => "{}"
  "shown" => "{}"
  "url" => "{}"
  "answers" => "{}"
  "datesubmitted" => "2015-04-15T05:46:30+00:00"
!>. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /Users/jeremy.mcnevin/Source/survey-gizmo-ruby/spec/support/spec_shared_api_object.rb:50:in `block (3 levels) in <top (required)>'.
......WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Actual error raised was #<SurveyGizmo::BadResponseError: There was an error!>. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /Users/jeremy.mcnevin/Source/survey-gizmo-ruby/spec/support/spec_shared_object_with_errors.rb:8:in `block (3 levels) in <top (required)>'.
WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Actual error raised was #<SurveyGizmo::BadResponseError: There was an error!>. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /Users/jeremy.mcnevin/Source/survey-gizmo-ruby/spec/support/spec_shared_object_with_errors.rb:9:in `block (3 levels) in <top (required)>'.
.....WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Actual error raised was #<SurveyGizmo::BadResponseError: something is wrong>. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /Users/jeremy.mcnevin/Source/survey-gizmo-ruby/spec/support/spec_shared_api_object.rb:33:in `block (3 levels) in <top (required)>'.
..WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Actual error raised was #<RuntimeError: No id; can't delete #<SurveyGizmo::API::Response:70243103995020>
  "survey_id" => "1234"
  "variable" => "{}"
  "meta" => "{}"
  "shown" => "{}"
  "url" => "{}"
  "answers" => "{}"
  "datesubmitted" => "2015-01-15T05:46:30+00:00"
!>. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /Users/jeremy.mcnevin/Source/survey-gizmo-ruby/spec/support/spec_shared_api_object.rb:50:in `block (3 levels) in <top (required)>'.
......WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Actual error raised was #<SurveyGizmo::BadResponseError: There was an error!>. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /Users/jeremy.mcnevin/Source/survey-gizmo-ruby/spec/support/spec_shared_object_with_errors.rb:8:in `block (3 levels) in <top (required)>'.
WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Actual error raised was #<SurveyGizmo::BadResponseError: There was an error!>. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /Users/jeremy.mcnevin/Source/survey-gizmo-ruby/spec/support/spec_shared_object_with_errors.rb:9:in `block (3 levels) in <top (required)>'.
...*

Pending: (Failures listed here are expected and do not affect your suite's status)

  1) Survey Gizmo Resource SurveyGizmo::API::AccountTeams Need an account with admin privileges to test this
     # Not yet implemented
     # ./spec/resource_spec.rb:299


Deprecation Warnings:

Using `should` from rspec-expectations' old `:should` syntax without explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or explicitly enable `:should` with `config.expect_with(:rspec) { |c| c.syntax = :should }` instead. Called from /Users/jeremy.mcnevin/Source/survey-gizmo-ruby/spec/support/spec_shared_api_object.rb:3:in `block (2 levels) in <top (required)>'.


If you need more of the backtrace for any of these deprecations to
identify where to make the necessary changes, you can configure
`config.raise_errors_for_deprecations!`, and it will turn the
deprecation warnings into errors, giving you the full backtrace.

1 deprecation warning total

Finished in 1.43 seconds (files took 1.45 seconds to load)
117 examples, 0 failures, 1 pending