PyRuby blog » testing http://www.pyruby.com Just another WordPress weblog Mon, 12 Dec 2011 11:03:27 +0000 en hourly 1 http://wordpress.org/?v=3.1.2 Stubserver 0.1 released http://www.pyruby.com/2010/02/23/stubserver-0-1-released/ http://www.pyruby.com/2010/02/23/stubserver-0-1-released/#comments Wed, 24 Feb 2010 04:03:41 +0000 PyRuby http://www.pyruby.com/?p=63 I’ve released a python stub webserver, described in an earlier blog post, on pypi. The features include support for any method (i.e. PUT, POST, DELETE, GET, RHUBARB …), handles chunked encoding, and supports capturing data passed for later assertions.

Because it’s on pypi, you can install using:-

pip install stubserver

or

easy_install stubserver

The verification model is [...]]]> I’ve released a python stub webserver, described in an earlier blog post, on pypi. The features include support for any method (i.e. PUT, POST, DELETE, GET, RHUBARB …), handles chunked encoding, and supports capturing data passed for later assertions.

Because it’s on pypi, you can install using:-

pip install stubserver

or

easy_install stubserver

The verification model is very simplistic, each registered expectation is only expected to occur once. To get more details, please refer to the documentation.

]]> http://www.pyruby.com/2010/02/23/stubserver-0-1-released/feed/ 0 Stubbing a REST api in Python http://www.pyruby.com/2009/10/06/stubbing-a-rest-api-in-python/ http://www.pyruby.com/2009/10/06/stubbing-a-rest-api-in-python/#comments Wed, 07 Oct 2009 04:58:19 +0000 PyRuby http://www.pyruby.com/?p=15 For the last few jobs I’ve had, Service Oriented Architecture has been a strong theme. Having services presenting REST apis that consume and produce XML has been the regular approach. When it comes to testing consumers of those services, I have found Python to be an extremely useful and convenient tool. It’s [...]]]> For the last few jobs I’ve had, Service Oriented Architecture has been a strong theme. Having services presenting REST apis that consume and produce XML has been the regular approach. When it comes to testing consumers of those services, I have found Python to be an extremely useful and convenient tool. It’s quick and easy to throw an HTTP server up in Python, and hard code the values that it returns. The problem is though, that I have ended up just adding code to the do_GET / do_POST methods as I add tests that handle different expectations. This ends up separating the expectations and return values from the test, and making maintaining the stub code harder than it should be.

To resolve this, I’d like to add expectations of the stub http server in the same way as with defining mocks. The syntax would look something like this

  1.    server.expect(method="GET", url="/address/\d+$").
  2.         and_return(mime="text/xml", file_content="path/to/response.xml")
  3.     capture = {}
  4.     server.expect(method="PUT", url="/address/\d+$", data_capture=capture).
  5.         and_return(reply_code=201)
  6.     server.expect(method="POST", url="address/\d+/inhabitant", data=‘<inhabitant name="Chris"/>’).
  7.         and_return(reply_code=204)
  8.     server.expect(method="GET", url="/monitor/server_status$").
  9.         and_return(content="<html><body>Server is up</body></html>", mime_type="text/html")
  10.     # execute system under test
  11.     self.assertEquals("<expected><xml/></expected>", capture["body"])
  12.  

So, over the next couple of weeks I’ll be putting this together, which should among other things allow me to improve the end to end testing story for djangoRESTModel.

]]> http://www.pyruby.com/2009/10/06/stubbing-a-rest-api-in-python/feed/ 1