Tests for :class:`StubTreq`.
Method | test |
Cookies manually specified as part of a dictionary are not relayed through redirects to different domains. |
Method | test |
Cookies manually specified as part of a dictionary are relayed through redirects to the same domain. |
Method | test |
Cookies will be sent for URLs that specify a non-default port for their scheme. |
Method | test |
StubTreq does not handle files yet - it should reject requests which attempt to pass files. |
Method | test |
Handle a resource returning NOT_DONE_YET and then canceling the request. |
Method | test |
Invalid URLs errback with a :obj:`SchemeNotSupported` failure, and does so even after a successful request. |
Method | test |
Handle a resource returning NOT_DONE_YET and then later finishing the response. |
Method | test |
Handle a resource returning NOT_DONE_YET and then sending some data in the response. |
Method | test |
Handle a resource returning NOT_DONE_YET and then streaming data back gradually over time. |
Method | test |
StubTreq rejects data that isn't list/dictionary/tuple/bytes/unicode. |
Method | test |
The resource provided to StubTreq responds to every request no matter what the URI or parameters or data. |
Method | test |
Calling request.getSession() in the wrapped resource will return a session with the same ID, until the sessions are cleaned; in other words, cookies are propagated between requests when the result of C{response... |
Method | test |
Every single function and attribute exposed by :obj:`treq.__all__` is provided by :obj:`StubTreq`. |
Cookies manually specified as part of a dictionary are not relayed through redirects to different domains. (This is really more of a test for scoping of cookies within treq itself, rather than just for testing.)
Cookies manually specified as part of a dictionary are relayed through redirects to the same domain. (This is really more of a test for scoping of cookies within treq itself, rather than just for testing.)
Cookies will be sent for URLs that specify a non-default port for their scheme. (This is really more of a test for scoping of cookies within treq itself, rather than just for testing.)
Invalid URLs errback with a :obj:`SchemeNotSupported` failure, and does so even after a successful request.
The resource provided to StubTreq responds to every request no matter what the URI or parameters or data.
Calling request.getSession() in the wrapped resource will return a session with the same ID, until the sessions are cleaned; in other words, cookies are propagated between requests when the result of C{response.cookies()} is passed to the next request.