Project

General

Profile

Bug #8300

TemplateTest#test_template_requests_return_data uses invalid "message" webmock option

Added by Dominic Cleal about 6 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Urgent
Assignee:
Category:
Tests
Target version:
Difficulty:
Triaged:
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

An invalid option is passed to webmock, which throws an exception since 1.20.3.

Unknown key: "message". Valid keys are: "headers", "status", "body", "exception", "should_timeout" (ArgumentError)
/usr/local/rvm/gems/ruby-1.9.3-p392@test_proxy_develop-2/gems/webmock-1.20.3/lib/webmock/util/hash_validator.rb:12:in `block in validate_keys'
/usr/local/rvm/gems/ruby-1.9.3-p392@test_proxy_develop-2/gems/webmock-1.20.3/lib/webmock/util/hash_validator.rb:10:in `each_key'
/usr/local/rvm/gems/ruby-1.9.3-p392@test_proxy_develop-2/gems/webmock-1.20.3/lib/webmock/util/hash_validator.rb:10:in `validate_keys'
/usr/local/rvm/gems/ruby-1.9.3-p392@test_proxy_develop-2/gems/webmock-1.20.3/lib/webmock/response.rb:80:in `options='
/usr/local/rvm/gems/ruby-1.9.3-p392@test_proxy_develop-2/gems/webmock-1.20.3/lib/webmock/response.rb:25:in `initialize'
/usr/local/rvm/gems/ruby-1.9.3-p392@test_proxy_develop-2/gems/webmock-1.20.3/lib/webmock/response.rb:15:in `new'
/usr/local/rvm/gems/ruby-1.9.3-p392@test_proxy_develop-2/gems/webmock-1.20.3/lib/webmock/response.rb:15:in `response_for'
/usr/local/rvm/gems/ruby-1.9.3-p392@test_proxy_develop-2/gems/webmock-1.20.3/lib/webmock/request_stub.rb:21:in `block in to_return'
/usr/local/rvm/gems/ruby-1.9.3-p392@test_proxy_develop-2/gems/webmock-1.20.3/lib/webmock/request_stub.rb:21:in `map'
/usr/local/rvm/gems/ruby-1.9.3-p392@test_proxy_develop-2/gems/webmock-1.20.3/lib/webmock/request_stub.rb:21:in `to_return'
/var/lib/workspace/workspace/test_proxy_develop/puppet/3.4.0/ruby/1.9.3/test/templates/template_test.rb:18:in `test_template_requests_return_data'

Associated revisions

Revision c422820a (diff)
Added by Dominic Cleal about 6 years ago

fixes #8300 - set webmock custom HTTP status response correctly

History

#1 Updated by Dominic Cleal about 6 years ago

  • Status changed from New to Assigned
  • Assignee set to Dominic Cleal

#2 Updated by The Foreman Bot about 6 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/smart-proxy/pull/234 added
  • Pull request deleted ()

#3 Updated by Dominic Cleal about 6 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF