Everything in requests eventually goes through an adapter to do the transport work. requests-mock creates a custom adapter that allows you to predefine responses when certain URIs are called.
There are then a number of methods provided to get the adapter used.
A simple example:
>>> import requests >>> import requests_mock >>> session = requests.Session() >>> adapter = requests_mock.Adapter() >>> session.mount('mock://', adapter) >>> adapter.register_uri('GET', 'mock://test.com', text='data') >>> resp = session.get('mock://test.com') >>> resp.status_code, resp.text (200, 'data')
Obviously having all URLs be mock:// prefixed isn't going to be useful, so you can use requests_mock.Mocker to get the adapter into place.
As a context manager:
>>> with requests_mock.Mocker() as m: ... m.get('http://test.com', text='data') ... requests.get('http://test.com').text ... 'data'
Or as a decorator:
>>> @requests_mock.Mocker() ... def test_func(m): ... m.get('http://test.com', text='data') ... return requests.get('http://test.com').text ... >>> test_func() 'data'
Or as a pytest fixture:
>>> def test_simple(requests_mock): ... requests_mock.get('http://test.com', text='data') ... assert 'data' == requests.get('http://test.com').text
For more information checkout the docs.
Development and bug tracking is performed on GitHub.
There is a tag dedicated to requests-mock on StackOverflow where you can ask usage questions.
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.