How to test Chef::REST.run_request


#1

In order to write a test for CHEF-269, I need to write a test for
Chef::REST.run_request. Unfortunately, this code is prefixed with

   # TODO - Figure out how to test this block - I really have no  

idea how
# to do it without actually calling http.request…

So, what is the best way to approach this?

/Jeppe


#2

On 13/07/2009, at 10:57 PM, Jeppe Nejsum Madsen wrote:

In order to write a test for CHEF-269, I need to write a test for
Chef::REST.run_request. Unfortunately, this code is prefixed with

 # TODO - Figure out how to test this block - I really have no  

idea how
# to do it without actually calling http.request…

So, what is the best way to approach this?

Looks to be a legacy TODO - there are functioning tests for
#run_request:

Regards,


AJ Christensen, Software Engineer
Opscode, Inc.
E: aj@opscode.com


#3

On 13/07/2009, at 13.00, Arjuna Christensen wrote:

On 13/07/2009, at 10:57 PM, Jeppe Nejsum Madsen wrote:

In order to write a test for CHEF-269, I need to write a test for
Chef::REST.run_request. Unfortunately, this code is prefixed with

 # TODO - Figure out how to test this block - I really have no  

idea how
# to do it without actually calling http.request…

So, what is the best way to approach this?

Looks to be a legacy TODO - there are functioning tests for
#run_request:

http://github.com/opscode/chef/blob/94b6530e69f3f50dcce11990a922ec7a5bd02706/chef/spec/unit/rest_spec.rb#L93

Ahh thanks. So, I actually succeeded in creating a fix, complete with
spec and everything (not bad for a Java/Scala guy, eh :-).

If somebody want to do a sanity check: http://github.com/jeppenejsum/chef/tree/CHEF-269

/Jeppe