Provide better dummy request/response for testing

[kevin]

From Matthew Clark on the mailing list:

Here is the beginning of a unittest that we have been using.  I should move this up to a parent class.  Otherwise it needs to be in each unittest --

class DummyResponse:
    def __init__(self):
        self.headerMap = {}
        self.simpleCookie = Cookie.SimpleCookie()
        self.version = "1.1"

    def purge__(self):
        pass

class DummyRequest:
    def __init__(self):
        self.approot = "/"
        self.headerMap = {}
        self.browserUrl = "http://testapp/"
        self.simpleCookie = Cookie.SimpleCookie()
    def purge__(self):
        pass


oldrequest = None
oldresponse = None

class QDBInterfaceTest(unittest.TestCase):

    def setUp(self):
        global oldrequest
        global oldresponse
        cherrypy.config.update(file="---dev.cfg")
        cherrypy.response = DummyResponse()
        cherrypy.request = DummyRequest()

    def tearDown(self):
        cherrypy.request = oldrequest
        cherrypy.response = oldresponse

[jorge.vargas]

what exactly is this for? is this really fastdata it seems like the spammer move it there.

[fumanchu@…]

FWIW, CherryPy? 3 will have dummy request/response objects in the main thread.

[alberto]

Batch moved into unclassified from 1.1 to properly track progress on the later

[mramm]

We should use webtest for tests, and provide full Request and Response objects in testing.