=======
This tool provides an in-process WSGI server on an ephemeral port.
It is intended for use in unit tests, when the system under test makes outgoing HTTP connections that cannot easily be mocked.
Usage
-----
First, create a WSGI application that represents the fake web server you want to create.
This is simpler than it seems; for example::
def simple_app(environ, start_response):
status = '200 OK'
headers = [('Content-type', 'text/plain')]
start_response(status, headers)
return ['Hello, world!\n']
Next, activate the test server.
There are several ways to do this, but all of them produce a port number.
As a context manager::
from mockweb import mock_server
def test_web_request():
with mock_server(simple_app) as port:
my_client.get_greeting('http://127.0.0.1:{}'.format(port))
As a decorator::
from mockweb import mock_server
@mock_server(simple_app)
def test_web_request(port):
my_client.get_greeting('http://127.0.0.1:{}'.format(port))
Or manually started and stopped::
from mockweb import mock_server
@mock_server
def test_web_request():
server = mock_server(simple_app)
# ...
server.start()
my_client.get_greeting('http://127.0.0.1:{}'.format(port))
server.stop()
In the latter case, be careful to stop the server.
Mock App
--------
The ``webmock`` package includes a simple WSGI app which behaves like the Python ``Mock``: it accepts and records any request, and allows tests to make assertions after the operation is complete.
Its usage is simple:
from mockweb import mock_server, MockApp
app = MockApp()
with mock_server(app):
# ..
app.assert_called_with('GET /foo/bar')
The assertion methods available are:
* ``assert_called_with(call)`` -- assert that the most recent request matches ``call``
* ``assert_called_once_with(call)`` -- assert that only one request was made and that it matches ``call``
* ``assert_any_call(call)`` -- assert that the any request matches ``call``
* ``assert_has_call([call, call, ..], any_order=False)`` -- assert that the given calls all occurred.
If ``any_order`` is false, the calls must be sequential.
A call can be described with a string containing the method and the path.
The mock app's behavior can be adjusted in some minor ways.
For anything more complex, build a custom WSGI app.
* ``MockApp(response='403 Forbidden')`` -- customize the HTTP response (default is "200 OK")
* ``MockApp(body='hello world\n')`` -- customize the response body (default is empty)
* ``MockApp(headers=[('X-Auth', 'abc123')])`` -- customize the response headers
Metadata
Release files for webmock 1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| webmock-1.1.0-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for webmock-1.1.0-py2.py3-none-any.whl |
Release files / webmock-1.1.0-py2.py3-none-any.whl
| Download URL | webmock-1.1.0-py2.py3-none-any.whl |
|---|---|
| Size | 6.3 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
b5d91585b0d942288ba04e8bb045024f68a83dcb3051f6c8a11e90c79be94628
|
|
BLAKE2b-256 checksum How to use checksums |
0acab5fb523b7d5613374dced997e006c1626955278f557f054f923974c444d1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for webmock 1.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.