{"id":13461719,"url":"https://github.com/getsentry/responses","last_synced_at":"2025-09-09T21:25:33.124Z","repository":{"id":11876939,"uuid":"14437755","full_name":"getsentry/responses","owner":"getsentry","description":"A utility for mocking out the Python Requests library.","archived":false,"fork":false,"pushed_at":"2025-03-11T15:38:09.000Z","size":762,"stargazers_count":4249,"open_issues_count":30,"forks_count":357,"subscribers_count":102,"default_branch":"master","last_synced_at":"2025-05-12T13:06:16.112Z","etag":null,"topics":["tag-production"],"latest_commit_sha":null,"homepage":"","language":"Python","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/getsentry.png","metadata":{"files":{"readme":"README.rst","changelog":"CHANGES","contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null},"funding":{"custom":["https://sentry.io/pricing/","https://sentry.io/"]}},"created_at":"2013-11-15T23:28:18.000Z","updated_at":"2025-05-11T12:25:33.000Z","dependencies_parsed_at":"2024-02-13T22:29:31.284Z","dependency_job_id":"2ace38d5-fafa-4094-bec9-40ba3cc54a01","html_url":"https://github.com/getsentry/responses","commit_stats":{"total_commits":625,"total_committers":136,"mean_commits":4.595588235294118,"dds":0.7824,"last_synced_commit":"93d321222c79b9b931d770fbd94020bad0294297"},"previous_names":[],"tags_count":63,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/getsentry%2Fresponses","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/getsentry%2Fresponses/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/getsentry%2Fresponses/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/getsentry%2Fresponses/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/getsentry","download_url":"https://codeload.github.com/getsentry/responses/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":253745151,"owners_count":21957317,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["tag-production"],"created_at":"2024-07-31T11:00:54.358Z","updated_at":"2025-05-12T13:06:33.960Z","avatar_url":"https://github.com/getsentry.png","language":"Python","readme":"Responses\n=========\n\n.. image:: https://img.shields.io/pypi/v/responses.svg\n    :target: https://pypi.python.org/pypi/responses/\n\n.. image:: https://img.shields.io/pypi/pyversions/responses.svg\n    :target: https://pypi.org/project/responses/\n\n.. image:: https://img.shields.io/pypi/dm/responses\n   :target: https://pypi.python.org/pypi/responses/\n\n.. image:: https://codecov.io/gh/getsentry/responses/branch/master/graph/badge.svg\n    :target: https://codecov.io/gh/getsentry/responses/\n\nA utility library for mocking out the ``requests`` Python library.\n\n..  note::\n\n    Responses requires Python 3.8 or newer, and requests \u003e= 2.30.0\n\n\nTable of Contents\n-----------------\n\n.. contents::\n\n\nInstalling\n----------\n\n``pip install responses``\n\n\nDeprecations and Migration Path\n-------------------------------\n\nHere you will find a list of deprecated functionality and a migration path for each.\nPlease ensure to update your code according to the guidance.\n\n.. list-table:: Deprecation and Migration\n   :widths: 50 25 50\n   :header-rows: 1\n\n   * - Deprecated Functionality\n     - Deprecated in Version\n     - Migration Path\n   * - ``responses.json_params_matcher``\n     - 0.14.0\n     - ``responses.matchers.json_params_matcher``\n   * - ``responses.urlencoded_params_matcher``\n     - 0.14.0\n     - ``responses.matchers.urlencoded_params_matcher``\n   * - ``stream`` argument in ``Response`` and ``CallbackResponse``\n     - 0.15.0\n     - Use ``stream`` argument in request directly.\n   * - ``match_querystring`` argument in ``Response`` and ``CallbackResponse``.\n     - 0.17.0\n     - Use ``responses.matchers.query_param_matcher`` or ``responses.matchers.query_string_matcher``\n   * - ``responses.assert_all_requests_are_fired``, ``responses.passthru_prefixes``, ``responses.target``\n     - 0.20.0\n     - Use ``responses.mock.assert_all_requests_are_fired``,\n       ``responses.mock.passthru_prefixes``, ``responses.mock.target`` instead.\n\nBasics\n------\n\nThe core of ``responses`` comes from registering mock responses and covering test function\nwith ``responses.activate`` decorator. ``responses`` provides similar interface as ``requests``.\n\nMain Interface\n^^^^^^^^^^^^^^\n\n* responses.add(``Response`` or ``Response args``) - allows either to register ``Response`` object or directly\n  provide arguments of ``Response`` object. See `Response Parameters`_\n\n.. code-block:: python\n\n    import responses\n    import requests\n\n\n    @responses.activate\n    def test_simple():\n        # Register via 'Response' object\n        rsp1 = responses.Response(\n            method=\"PUT\",\n            url=\"http://example.com\",\n        )\n        responses.add(rsp1)\n        # register via direct arguments\n        responses.add(\n            responses.GET,\n            \"http://twitter.com/api/1/foobar\",\n            json={\"error\": \"not found\"},\n            status=404,\n        )\n\n        resp = requests.get(\"http://twitter.com/api/1/foobar\")\n        resp2 = requests.put(\"http://example.com\")\n\n        assert resp.json() == {\"error\": \"not found\"}\n        assert resp.status_code == 404\n\n        assert resp2.status_code == 200\n        assert resp2.request.method == \"PUT\"\n\n\nIf you attempt to fetch a url which doesn't hit a match, ``responses`` will raise\na ``ConnectionError``:\n\n.. code-block:: python\n\n    import responses\n    import requests\n\n    from requests.exceptions import ConnectionError\n\n\n    @responses.activate\n    def test_simple():\n        with pytest.raises(ConnectionError):\n            requests.get(\"http://twitter.com/api/1/foobar\")\n\n\nShortcuts\n^^^^^^^^^\n\nShortcuts provide a shorten version of ``responses.add()`` where method argument is prefilled\n\n* responses.delete(``Response args``) - register DELETE response\n* responses.get(``Response args``) - register GET response\n* responses.head(``Response args``) - register HEAD response\n* responses.options(``Response args``) - register OPTIONS response\n* responses.patch(``Response args``) - register PATCH response\n* responses.post(``Response args``) - register POST response\n* responses.put(``Response args``) - register PUT response\n\n.. code-block:: python\n\n    import responses\n    import requests\n\n\n    @responses.activate\n    def test_simple():\n        responses.get(\n            \"http://twitter.com/api/1/foobar\",\n            json={\"type\": \"get\"},\n        )\n\n        responses.post(\n            \"http://twitter.com/api/1/foobar\",\n            json={\"type\": \"post\"},\n        )\n\n        responses.patch(\n            \"http://twitter.com/api/1/foobar\",\n            json={\"type\": \"patch\"},\n        )\n\n        resp_get = requests.get(\"http://twitter.com/api/1/foobar\")\n        resp_post = requests.post(\"http://twitter.com/api/1/foobar\")\n        resp_patch = requests.patch(\"http://twitter.com/api/1/foobar\")\n\n        assert resp_get.json() == {\"type\": \"get\"}\n        assert resp_post.json() == {\"type\": \"post\"}\n        assert resp_patch.json() == {\"type\": \"patch\"}\n\nResponses as a context manager\n^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n\nInstead of wrapping the whole function with decorator you can use a context manager.\n\n.. code-block:: python\n\n    import responses\n    import requests\n\n\n    def test_my_api():\n        with responses.RequestsMock() as rsps:\n            rsps.add(\n                responses.GET,\n                \"http://twitter.com/api/1/foobar\",\n                body=\"{}\",\n                status=200,\n                content_type=\"application/json\",\n            )\n            resp = requests.get(\"http://twitter.com/api/1/foobar\")\n\n            assert resp.status_code == 200\n\n        # outside the context manager requests will hit the remote server\n        resp = requests.get(\"http://twitter.com/api/1/foobar\")\n        resp.status_code == 404\n\n\nResponse Parameters\n-------------------\n\nThe following attributes can be passed to a Response mock:\n\nmethod (``str``)\n    The HTTP method (GET, POST, etc).\n\nurl (``str`` or ``compiled regular expression``)\n    The full resource URL.\n\nmatch_querystring (``bool``)\n    DEPRECATED: Use ``responses.matchers.query_param_matcher`` or\n    ``responses.matchers.query_string_matcher``\n\n    Include the query string when matching requests.\n    Enabled by default if the response URL contains a query string,\n    disabled if it doesn't or the URL is a regular expression.\n\nbody (``str`` or ``BufferedReader`` or ``Exception``)\n    The response body. Read more `Exception as Response body`_\n\njson\n    A Python object representing the JSON response body. Automatically configures\n    the appropriate Content-Type.\n\nstatus (``int``)\n    The HTTP status code.\n\ncontent_type (``content_type``)\n    Defaults to ``text/plain``.\n\nheaders (``dict``)\n    Response headers.\n\nstream (``bool``)\n    DEPRECATED: use ``stream`` argument in request directly\n\nauto_calculate_content_length (``bool``)\n    Disabled by default. Automatically calculates the length of a supplied string or JSON body.\n\nmatch (``tuple``)\n    An iterable (``tuple`` is recommended) of callbacks to match requests\n    based on request attributes.\n    Current module provides multiple matchers that you can use to match:\n\n    * body contents in JSON format\n    * body contents in URL encoded data format\n    * request query parameters\n    * request query string (similar to query parameters but takes string as input)\n    * kwargs provided to request e.g. ``stream``, ``verify``\n    * 'multipart/form-data' content and headers in request\n    * request headers\n    * request fragment identifier\n\n    Alternatively user can create custom matcher.\n    Read more `Matching Requests`_\n\n\nException as Response body\n--------------------------\n\nYou can pass an ``Exception`` as the body to trigger an error on the request:\n\n.. code-block:: python\n\n    import responses\n    import requests\n\n\n    @responses.activate\n    def test_simple():\n        responses.get(\"http://twitter.com/api/1/foobar\", body=Exception(\"...\"))\n        with pytest.raises(Exception):\n            requests.get(\"http://twitter.com/api/1/foobar\")\n\n\nMatching Requests\n-----------------\n\nMatching Request Body Contents\n^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n\nWhen adding responses for endpoints that are sent request data you can add\nmatchers to ensure your code is sending the right parameters and provide\ndifferent responses based on the request body contents. ``responses`` provides\nmatchers for JSON and URL-encoded request bodies.\n\nURL-encoded data\n\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\n\n.. code-block:: python\n\n    import responses\n    import requests\n    from responses import matchers\n\n\n    @responses.activate\n    def test_calc_api():\n        responses.post(\n            url=\"http://calc.com/sum\",\n            body=\"4\",\n            match=[matchers.urlencoded_params_matcher({\"left\": \"1\", \"right\": \"3\"})],\n        )\n        requests.post(\"http://calc.com/sum\", data={\"left\": 1, \"right\": 3})\n\n\nJSON encoded data\n\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\n\nMatching JSON encoded data can be done with ``matchers.json_params_matcher()``.\n\n.. code-block:: python\n\n    import responses\n    import requests\n    from responses import matchers\n\n\n    @responses.activate\n    def test_calc_api():\n        responses.post(\n            url=\"http://example.com/\",\n            body=\"one\",\n            match=[\n                matchers.json_params_matcher({\"page\": {\"name\": \"first\", \"type\": \"json\"}})\n            ],\n        )\n        resp = requests.request(\n            \"POST\",\n            \"http://example.com/\",\n            headers={\"Content-Type\": \"application/json\"},\n            json={\"page\": {\"name\": \"first\", \"type\": \"json\"}},\n        )\n\n\nQuery Parameters Matcher\n^^^^^^^^^^^^^^^^^^^^^^^^\n\nQuery Parameters as a Dictionary\n\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\n\nYou can use the ``matchers.query_param_matcher`` function to match\nagainst the ``params`` request parameter. Just use the same dictionary as you\nwill use in ``params`` argument in ``request``.\n\nNote, do not use query parameters as part of the URL. Avoid using ``match_querystring``\ndeprecated argument.\n\n.. code-block:: python\n\n    import responses\n    import requests\n    from responses import matchers\n\n\n    @responses.activate\n    def test_calc_api():\n        url = \"http://example.com/test\"\n        params = {\"hello\": \"world\", \"I am\": \"a big test\"}\n        responses.get(\n            url=url,\n            body=\"test\",\n            match=[matchers.query_param_matcher(params)],\n        )\n\n        resp = requests.get(url, params=params)\n\n        constructed_url = r\"http://example.com/test?I+am=a+big+test\u0026hello=world\"\n        assert resp.url == constructed_url\n        assert resp.request.url == constructed_url\n        assert resp.request.params == params\n\nBy default, matcher will validate that all parameters match strictly.\nTo validate that only parameters specified in the matcher are present in original request\nuse ``strict_match=False``.\n\nQuery Parameters as a String\n\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\n\nAs alternative, you can use query string value in ``matchers.query_string_matcher`` to match\nquery parameters in your request\n\n.. code-block:: python\n\n    import requests\n    import responses\n    from responses import matchers\n\n\n    @responses.activate\n    def my_func():\n        responses.get(\n            \"https://httpbin.org/get\",\n            match=[matchers.query_string_matcher(\"didi=pro\u0026test=1\")],\n        )\n        resp = requests.get(\"https://httpbin.org/get\", params={\"test\": 1, \"didi\": \"pro\"})\n\n\n    my_func()\n\n\nRequest Keyword Arguments Matcher\n^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n\nTo validate request arguments use the ``matchers.request_kwargs_matcher`` function to match\nagainst the request kwargs.\n\nOnly following arguments are supported: ``timeout``, ``verify``, ``proxies``, ``stream``, ``cert``.\n\nNote, only arguments provided to ``matchers.request_kwargs_matcher`` will be validated.\n\n.. code-block:: python\n\n    import responses\n    import requests\n    from responses import matchers\n\n    with responses.RequestsMock(assert_all_requests_are_fired=False) as rsps:\n        req_kwargs = {\n            \"stream\": True,\n            \"verify\": False,\n        }\n        rsps.add(\n            \"GET\",\n            \"http://111.com\",\n            match=[matchers.request_kwargs_matcher(req_kwargs)],\n        )\n\n        requests.get(\"http://111.com\", stream=True)\n\n        # \u003e\u003e\u003e  Arguments don't match: {stream: True, verify: True} doesn't match {stream: True, verify: False}\n\n\nRequest multipart/form-data Data Validation\n^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n\nTo validate request body and headers for ``multipart/form-data`` data you can use\n``matchers.multipart_matcher``. The ``data``, and ``files`` parameters provided will be compared\nto the request:\n\n.. code-block:: python\n\n    import requests\n    import responses\n    from responses.matchers import multipart_matcher\n\n\n    @responses.activate\n    def my_func():\n        req_data = {\"some\": \"other\", \"data\": \"fields\"}\n        req_files = {\"file_name\": b\"Old World!\"}\n        responses.post(\n            url=\"http://httpbin.org/post\",\n            match=[multipart_matcher(req_files, data=req_data)],\n        )\n        resp = requests.post(\"http://httpbin.org/post\", files={\"file_name\": b\"New World!\"})\n\n\n    my_func()\n    # \u003e\u003e\u003e raises ConnectionError: multipart/form-data doesn't match. Request body differs.\n\nRequest Fragment Identifier Validation\n^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n\nTo validate request URL fragment identifier you can use ``matchers.fragment_identifier_matcher``.\nThe matcher takes fragment string (everything after ``#`` sign) as input for comparison:\n\n.. code-block:: python\n\n    import requests\n    import responses\n    from responses.matchers import fragment_identifier_matcher\n\n\n    @responses.activate\n    def run():\n        url = \"http://example.com?ab=xy\u0026zed=qwe#test=1\u0026foo=bar\"\n        responses.get(\n            url,\n            match=[fragment_identifier_matcher(\"test=1\u0026foo=bar\")],\n            body=b\"test\",\n        )\n\n        # two requests to check reversed order of fragment identifier\n        resp = requests.get(\"http://example.com?ab=xy\u0026zed=qwe#test=1\u0026foo=bar\")\n        resp = requests.get(\"http://example.com?zed=qwe\u0026ab=xy#foo=bar\u0026test=1\")\n\n\n    run()\n\nRequest Headers Validation\n^^^^^^^^^^^^^^^^^^^^^^^^^^\n\nWhen adding responses you can specify matchers to ensure that your code is\nsending the right headers and provide different responses based on the request\nheaders.\n\n.. code-block:: python\n\n    import responses\n    import requests\n    from responses import matchers\n\n\n    @responses.activate\n    def test_content_type():\n        responses.get(\n            url=\"http://example.com/\",\n            body=\"hello world\",\n            match=[matchers.header_matcher({\"Accept\": \"text/plain\"})],\n        )\n\n        responses.get(\n            url=\"http://example.com/\",\n            json={\"content\": \"hello world\"},\n            match=[matchers.header_matcher({\"Accept\": \"application/json\"})],\n        )\n\n        # request in reverse order to how they were added!\n        resp = requests.get(\"http://example.com/\", headers={\"Accept\": \"application/json\"})\n        assert resp.json() == {\"content\": \"hello world\"}\n\n        resp = requests.get(\"http://example.com/\", headers={\"Accept\": \"text/plain\"})\n        assert resp.text == \"hello world\"\n\nBecause ``requests`` will send several standard headers in addition to what was\nspecified by your code, request headers that are additional to the ones\npassed to the matcher are ignored by default. You can change this behaviour by\npassing ``strict_match=True`` to the matcher to ensure that only the headers\nthat you're expecting are sent and no others. Note that you will probably have\nto use a ``PreparedRequest`` in your code to ensure that ``requests`` doesn't\ninclude any additional headers.\n\n.. code-block:: python\n\n    import responses\n    import requests\n    from responses import matchers\n\n\n    @responses.activate\n    def test_content_type():\n        responses.get(\n            url=\"http://example.com/\",\n            body=\"hello world\",\n            match=[matchers.header_matcher({\"Accept\": \"text/plain\"}, strict_match=True)],\n        )\n\n        # this will fail because requests adds its own headers\n        with pytest.raises(ConnectionError):\n            requests.get(\"http://example.com/\", headers={\"Accept\": \"text/plain\"})\n\n        # a prepared request where you overwrite the headers before sending will work\n        session = requests.Session()\n        prepped = session.prepare_request(\n            requests.Request(\n                method=\"GET\",\n                url=\"http://example.com/\",\n            )\n        )\n        prepped.headers = {\"Accept\": \"text/plain\"}\n\n        resp = session.send(prepped)\n        assert resp.text == \"hello world\"\n\n\nCreating Custom Matcher\n^^^^^^^^^^^^^^^^^^^^^^^\n\nIf your application requires other encodings or different data validation you can build\nyour own matcher that returns ``Tuple[matches: bool, reason: str]``.\nWhere boolean represents ``True`` or ``False`` if the request parameters match and\nthe string is a reason in case of match failure. Your matcher can\nexpect a ``PreparedRequest`` parameter to be provided by ``responses``.\n\nNote, ``PreparedRequest`` is customized and has additional attributes ``params`` and ``req_kwargs``.\n\nResponse Registry\n---------------------------\n\nDefault Registry\n^^^^^^^^^^^^^^^^\n\nBy default, ``responses`` will search all registered ``Response`` objects and\nreturn a match. If only one ``Response`` is registered, the registry is kept unchanged.\nHowever, if multiple matches are found for the same request, then first match is returned and\nremoved from registry.\n\nOrdered Registry\n^^^^^^^^^^^^^^^^\n\nIn some scenarios it is important to preserve the order of the requests and responses.\nYou can use ``registries.OrderedRegistry`` to force all ``Response`` objects to be dependent\non the insertion order and invocation index.\nIn following example we add multiple ``Response`` objects that target the same URL. However,\nyou can see, that status code will depend on the invocation order.\n\n\n.. code-block:: python\n\n    import requests\n\n    import responses\n    from responses.registries import OrderedRegistry\n\n\n    @responses.activate(registry=OrderedRegistry)\n    def test_invocation_index():\n        responses.get(\n            \"http://twitter.com/api/1/foobar\",\n            json={\"msg\": \"not found\"},\n            status=404,\n        )\n        responses.get(\n            \"http://twitter.com/api/1/foobar\",\n            json={\"msg\": \"OK\"},\n            status=200,\n        )\n        responses.get(\n            \"http://twitter.com/api/1/foobar\",\n            json={\"msg\": \"OK\"},\n            status=200,\n        )\n        responses.get(\n            \"http://twitter.com/api/1/foobar\",\n            json={\"msg\": \"not found\"},\n            status=404,\n        )\n\n        resp = requests.get(\"http://twitter.com/api/1/foobar\")\n        assert resp.status_code == 404\n        resp = requests.get(\"http://twitter.com/api/1/foobar\")\n        assert resp.status_code == 200\n        resp = requests.get(\"http://twitter.com/api/1/foobar\")\n        assert resp.status_code == 200\n        resp = requests.get(\"http://twitter.com/api/1/foobar\")\n        assert resp.status_code == 404\n\n\nCustom Registry\n^^^^^^^^^^^^^^^\n\nBuilt-in ``registries`` are suitable for most of use cases, but to handle special conditions, you can\nimplement custom registry which must follow interface of ``registries.FirstMatchRegistry``.\nRedefining the ``find`` method will allow you to create custom search logic and return\nappropriate ``Response``\n\nExample that shows how to set custom registry\n\n.. code-block:: python\n\n    import responses\n    from responses import registries\n\n\n    class CustomRegistry(registries.FirstMatchRegistry):\n        pass\n\n\n    print(\"Before tests:\", responses.mock.get_registry())\n    \"\"\" Before tests: \u003cresponses.registries.FirstMatchRegistry object\u003e \"\"\"\n\n\n    # using function decorator\n    @responses.activate(registry=CustomRegistry)\n    def run():\n        print(\"Within test:\", responses.mock.get_registry())\n        \"\"\" Within test: \u003c__main__.CustomRegistry object\u003e \"\"\"\n\n\n    run()\n\n    print(\"After test:\", responses.mock.get_registry())\n    \"\"\" After test: \u003cresponses.registries.FirstMatchRegistry object\u003e \"\"\"\n\n    # using context manager\n    with responses.RequestsMock(registry=CustomRegistry) as rsps:\n        print(\"In context manager:\", rsps.get_registry())\n        \"\"\" In context manager: \u003c__main__.CustomRegistry object\u003e \"\"\"\n\n    print(\"After exit from context manager:\", responses.mock.get_registry())\n    \"\"\"\n    After exit from context manager: \u003cresponses.registries.FirstMatchRegistry object\u003e\n    \"\"\"\n\nDynamic Responses\n-----------------\n\nYou can utilize callbacks to provide dynamic responses. The callback must return\na tuple of (``status``, ``headers``, ``body``).\n\n.. code-block:: python\n\n    import json\n\n    import responses\n    import requests\n\n\n    @responses.activate\n    def test_calc_api():\n        def request_callback(request):\n            payload = json.loads(request.body)\n            resp_body = {\"value\": sum(payload[\"numbers\"])}\n            headers = {\"request-id\": \"728d329e-0e86-11e4-a748-0c84dc037c13\"}\n            return (200, headers, json.dumps(resp_body))\n\n        responses.add_callback(\n            responses.POST,\n            \"http://calc.com/sum\",\n            callback=request_callback,\n            content_type=\"application/json\",\n        )\n\n        resp = requests.post(\n            \"http://calc.com/sum\",\n            json.dumps({\"numbers\": [1, 2, 3]}),\n            headers={\"content-type\": \"application/json\"},\n        )\n\n        assert resp.json() == {\"value\": 6}\n\n        assert len(responses.calls) == 1\n        assert responses.calls[0].request.url == \"http://calc.com/sum\"\n        assert responses.calls[0].response.text == '{\"value\": 6}'\n        assert (\n            responses.calls[0].response.headers[\"request-id\"]\n            == \"728d329e-0e86-11e4-a748-0c84dc037c13\"\n        )\n\nYou can also pass a compiled regex to ``add_callback`` to match multiple urls:\n\n.. code-block:: python\n\n    import re, json\n\n    from functools import reduce\n\n    import responses\n    import requests\n\n    operators = {\n        \"sum\": lambda x, y: x + y,\n        \"prod\": lambda x, y: x * y,\n        \"pow\": lambda x, y: x**y,\n    }\n\n\n    @responses.activate\n    def test_regex_url():\n        def request_callback(request):\n            payload = json.loads(request.body)\n            operator_name = request.path_url[1:]\n\n            operator = operators[operator_name]\n\n            resp_body = {\"value\": reduce(operator, payload[\"numbers\"])}\n            headers = {\"request-id\": \"728d329e-0e86-11e4-a748-0c84dc037c13\"}\n            return (200, headers, json.dumps(resp_body))\n\n        responses.add_callback(\n            responses.POST,\n            re.compile(\"http://calc.com/(sum|prod|pow|unsupported)\"),\n            callback=request_callback,\n            content_type=\"application/json\",\n        )\n\n        resp = requests.post(\n            \"http://calc.com/prod\",\n            json.dumps({\"numbers\": [2, 3, 4]}),\n            headers={\"content-type\": \"application/json\"},\n        )\n        assert resp.json() == {\"value\": 24}\n\n\n    test_regex_url()\n\n\nIf you want to pass extra keyword arguments to the callback function, for example when reusing\na callback function to give a slightly different result, you can use ``functools.partial``:\n\n.. code-block:: python\n\n    from functools import partial\n\n\n    def request_callback(request, id=None):\n        payload = json.loads(request.body)\n        resp_body = {\"value\": sum(payload[\"numbers\"])}\n        headers = {\"request-id\": id}\n        return (200, headers, json.dumps(resp_body))\n\n\n    responses.add_callback(\n        responses.POST,\n        \"http://calc.com/sum\",\n        callback=partial(request_callback, id=\"728d329e-0e86-11e4-a748-0c84dc037c13\"),\n        content_type=\"application/json\",\n    )\n\n\nIntegration with unit test frameworks\n-------------------------------------\n\nResponses as a ``pytest`` fixture\n^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n\nUse the pytest-responses package to export ``responses`` as a pytest fixture.\n\n``pip install pytest-responses``\n\nYou can then access it in a pytest script using:\n\n.. code-block:: python\n\n    import pytest_responses\n\n\n    def test_api(responses):\n        responses.get(\n            \"http://twitter.com/api/1/foobar\",\n            body=\"{}\",\n            status=200,\n            content_type=\"application/json\",\n        )\n        resp = requests.get(\"http://twitter.com/api/1/foobar\")\n        assert resp.status_code == 200\n\nAdd default responses for each test\n^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n\nWhen run with ``unittest`` tests, this can be used to set up some\ngeneric class-level responses, that may be complemented by each test.\nSimilar interface could be applied in ``pytest`` framework.\n\n.. code-block:: python\n\n    class TestMyApi(unittest.TestCase):\n        def setUp(self):\n            responses.get(\"https://example.com\", body=\"within setup\")\n            # here go other self.responses.add(...)\n\n        @responses.activate\n        def test_my_func(self):\n            responses.get(\n                \"https://httpbin.org/get\",\n                match=[matchers.query_param_matcher({\"test\": \"1\", \"didi\": \"pro\"})],\n                body=\"within test\",\n            )\n            resp = requests.get(\"https://example.com\")\n            resp2 = requests.get(\n                \"https://httpbin.org/get\", params={\"test\": \"1\", \"didi\": \"pro\"}\n            )\n            print(resp.text)\n            # \u003e\u003e\u003e within setup\n            print(resp2.text)\n            # \u003e\u003e\u003e within test\n\n\nRequestMock methods: start, stop, reset\n^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n\n``responses`` has ``start``, ``stop``, ``reset`` methods very analogous to\n`unittest.mock.patch \u003chttps://docs.python.org/3/library/unittest.mock.html#patch-methods-start-and-stop\u003e`_.\nThese make it simpler to do requests mocking in ``setup`` methods or where\nyou want to do multiple patches without nesting decorators or with statements.\n\n.. code-block:: python\n\n    class TestUnitTestPatchSetup:\n        def setup(self):\n            \"\"\"Creates ``RequestsMock`` instance and starts it.\"\"\"\n            self.r_mock = responses.RequestsMock(assert_all_requests_are_fired=True)\n            self.r_mock.start()\n\n            # optionally some default responses could be registered\n            self.r_mock.get(\"https://example.com\", status=505)\n            self.r_mock.put(\"https://example.com\", status=506)\n\n        def teardown(self):\n            \"\"\"Stops and resets RequestsMock instance.\n\n            If ``assert_all_requests_are_fired`` is set to ``True``, will raise an error\n            if some requests were not processed.\n            \"\"\"\n            self.r_mock.stop()\n            self.r_mock.reset()\n\n        def test_function(self):\n            resp = requests.get(\"https://example.com\")\n            assert resp.status_code == 505\n\n            resp = requests.put(\"https://example.com\")\n            assert resp.status_code == 506\n\n\nAssertions on declared responses\n--------------------------------\n\nWhen used as a context manager, Responses will, by default, raise an assertion\nerror if a url was registered but not accessed. This can be disabled by passing\nthe ``assert_all_requests_are_fired`` value:\n\n.. code-block:: python\n\n    import responses\n    import requests\n\n\n    def test_my_api():\n        with responses.RequestsMock(assert_all_requests_are_fired=False) as rsps:\n            rsps.add(\n                responses.GET,\n                \"http://twitter.com/api/1/foobar\",\n                body=\"{}\",\n                status=200,\n                content_type=\"application/json\",\n            )\n\nAssert Request Call Count\n-------------------------\n\nAssert based on ``Response`` object\n^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n\nEach ``Response`` object has ``call_count`` attribute that could be inspected\nto check how many times each request was matched.\n\n.. code-block:: python\n\n    @responses.activate\n    def test_call_count_with_matcher():\n        rsp = responses.get(\n            \"http://www.example.com\",\n            match=(matchers.query_param_matcher({}),),\n        )\n        rsp2 = responses.get(\n            \"http://www.example.com\",\n            match=(matchers.query_param_matcher({\"hello\": \"world\"}),),\n            status=777,\n        )\n        requests.get(\"http://www.example.com\")\n        resp1 = requests.get(\"http://www.example.com\")\n        requests.get(\"http://www.example.com?hello=world\")\n        resp2 = requests.get(\"http://www.example.com?hello=world\")\n\n        assert resp1.status_code == 200\n        assert resp2.status_code == 777\n\n        assert rsp.call_count == 2\n        assert rsp2.call_count == 2\n\nAssert based on the exact URL\n^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n\nAssert that the request was called exactly n times.\n\n.. code-block:: python\n\n    import responses\n    import requests\n\n\n    @responses.activate\n    def test_assert_call_count():\n        responses.get(\"http://example.com\")\n\n        requests.get(\"http://example.com\")\n        assert responses.assert_call_count(\"http://example.com\", 1) is True\n\n        requests.get(\"http://example.com\")\n        with pytest.raises(AssertionError) as excinfo:\n            responses.assert_call_count(\"http://example.com\", 1)\n        assert (\n            \"Expected URL 'http://example.com' to be called 1 times. Called 2 times.\"\n            in str(excinfo.value)\n        )\n\n\n    @responses.activate\n    def test_assert_call_count_always_match_qs():\n        responses.get(\"http://www.example.com\")\n        requests.get(\"http://www.example.com\")\n        requests.get(\"http://www.example.com?hello=world\")\n\n        # One call on each url, querystring is matched by default\n        responses.assert_call_count(\"http://www.example.com\", 1) is True\n        responses.assert_call_count(\"http://www.example.com?hello=world\", 1) is True\n\n\nAssert Request Calls data\n-------------------------\n\n``Request`` object has ``calls`` list which elements correspond to ``Call`` objects\nin the global list of ``Registry``. This can be useful when the order of requests is not\nguaranteed, but you need to check their correctness, for example in multithreaded\napplications.\n\n.. code-block:: python\n\n    import concurrent.futures\n    import responses\n    import requests\n\n\n    @responses.activate\n    def test_assert_calls_on_resp():\n        rsp1 = responses.patch(\"http://www.foo.bar/1/\", status=200)\n        rsp2 = responses.patch(\"http://www.foo.bar/2/\", status=400)\n        rsp3 = responses.patch(\"http://www.foo.bar/3/\", status=200)\n\n        def update_user(uid, is_active):\n            url = f\"http://www.foo.bar/{uid}/\"\n            response = requests.patch(url, json={\"is_active\": is_active})\n            return response\n\n        with concurrent.futures.ThreadPoolExecutor(max_workers=3) as executor:\n            future_to_uid = {\n                executor.submit(update_user, uid, is_active): uid\n                for (uid, is_active) in [(\"3\", True), (\"2\", True), (\"1\", False)]\n            }\n            for future in concurrent.futures.as_completed(future_to_uid):\n                uid = future_to_uid[future]\n                response = future.result()\n                print(f\"{uid} updated with {response.status_code} status code\")\n\n        assert len(responses.calls) == 3  # total calls count\n\n        assert rsp1.call_count == 1\n        assert rsp1.calls[0] in responses.calls\n        assert rsp1.calls[0].response.status_code == 200\n        assert json.loads(rsp1.calls[0].request.body) == {\"is_active\": False}\n\n        assert rsp2.call_count == 1\n        assert rsp2.calls[0] in responses.calls\n        assert rsp2.calls[0].response.status_code == 400\n        assert json.loads(rsp2.calls[0].request.body) == {\"is_active\": True}\n\n        assert rsp3.call_count == 1\n        assert rsp3.calls[0] in responses.calls\n        assert rsp3.calls[0].response.status_code == 200\n        assert json.loads(rsp3.calls[0].request.body) == {\"is_active\": True}\n\nMultiple Responses\n------------------\n\nYou can also add multiple responses for the same url:\n\n.. code-block:: python\n\n    import responses\n    import requests\n\n\n    @responses.activate\n    def test_my_api():\n        responses.get(\"http://twitter.com/api/1/foobar\", status=500)\n        responses.get(\n            \"http://twitter.com/api/1/foobar\",\n            body=\"{}\",\n            status=200,\n            content_type=\"application/json\",\n        )\n\n        resp = requests.get(\"http://twitter.com/api/1/foobar\")\n        assert resp.status_code == 500\n        resp = requests.get(\"http://twitter.com/api/1/foobar\")\n        assert resp.status_code == 200\n\n\nURL Redirection\n---------------\n\nIn the following example you can see how to create a redirection chain and add custom exception that will be raised\nin the execution chain and contain the history of redirects.\n\n..  code-block::\n\n    A -\u003e 301 redirect -\u003e B\n    B -\u003e 301 redirect -\u003e C\n    C -\u003e connection issue\n\n.. code-block:: python\n\n    import pytest\n    import requests\n\n    import responses\n\n\n    @responses.activate\n    def test_redirect():\n        # create multiple Response objects where first two contain redirect headers\n        rsp1 = responses.Response(\n            responses.GET,\n            \"http://example.com/1\",\n            status=301,\n            headers={\"Location\": \"http://example.com/2\"},\n        )\n        rsp2 = responses.Response(\n            responses.GET,\n            \"http://example.com/2\",\n            status=301,\n            headers={\"Location\": \"http://example.com/3\"},\n        )\n        rsp3 = responses.Response(responses.GET, \"http://example.com/3\", status=200)\n\n        # register above generated Responses in ``response`` module\n        responses.add(rsp1)\n        responses.add(rsp2)\n        responses.add(rsp3)\n\n        # do the first request in order to generate genuine ``requests`` response\n        # this object will contain genuine attributes of the response, like ``history``\n        rsp = requests.get(\"http://example.com/1\")\n        responses.calls.reset()\n\n        # customize exception with ``response`` attribute\n        my_error = requests.ConnectionError(\"custom error\")\n        my_error.response = rsp\n\n        # update body of the 3rd response with Exception, this will be raised during execution\n        rsp3.body = my_error\n\n        with pytest.raises(requests.ConnectionError) as exc_info:\n            requests.get(\"http://example.com/1\")\n\n        assert exc_info.value.args[0] == \"custom error\"\n        assert rsp1.url in exc_info.value.response.history[0].url\n        assert rsp2.url in exc_info.value.response.history[1].url\n\n\nValidate ``Retry`` mechanism\n----------------------------\n\nIf you are using the ``Retry`` features of ``urllib3`` and want to cover scenarios that test your retry limits, you can test those scenarios with ``responses`` as well. The best approach will be to use an `Ordered Registry`_\n\n.. code-block:: python\n\n    import requests\n\n    import responses\n    from responses import registries\n    from urllib3.util import Retry\n\n\n    @responses.activate(registry=registries.OrderedRegistry)\n    def test_max_retries():\n        url = \"https://example.com\"\n        rsp1 = responses.get(url, body=\"Error\", status=500)\n        rsp2 = responses.get(url, body=\"Error\", status=500)\n        rsp3 = responses.get(url, body=\"Error\", status=500)\n        rsp4 = responses.get(url, body=\"OK\", status=200)\n\n        session = requests.Session()\n\n        adapter = requests.adapters.HTTPAdapter(\n            max_retries=Retry(\n                total=4,\n                backoff_factor=0.1,\n                status_forcelist=[500],\n                method_whitelist=[\"GET\", \"POST\", \"PATCH\"],\n            )\n        )\n        session.mount(\"https://\", adapter)\n\n        resp = session.get(url)\n\n        assert resp.status_code == 200\n        assert rsp1.call_count == 1\n        assert rsp2.call_count == 1\n        assert rsp3.call_count == 1\n        assert rsp4.call_count == 1\n\n\nUsing a callback to modify the response\n---------------------------------------\n\nIf you use customized processing in ``requests`` via subclassing/mixins, or if you\nhave library tools that interact with ``requests`` at a low level, you may need\nto add extended processing to the mocked Response object to fully simulate the\nenvironment for your tests.  A ``response_callback`` can be used, which will be\nwrapped by the library before being returned to the caller.  The callback\naccepts a ``response`` as it's single argument, and is expected to return a\nsingle ``response`` object.\n\n.. code-block:: python\n\n    import responses\n    import requests\n\n\n    def response_callback(resp):\n        resp.callback_processed = True\n        return resp\n\n\n    with responses.RequestsMock(response_callback=response_callback) as m:\n        m.add(responses.GET, \"http://example.com\", body=b\"test\")\n        resp = requests.get(\"http://example.com\")\n        assert resp.text == \"test\"\n        assert hasattr(resp, \"callback_processed\")\n        assert resp.callback_processed is True\n\n\nPassing through real requests\n-----------------------------\n\nIn some cases you may wish to allow for certain requests to pass through responses\nand hit a real server. This can be done with the ``add_passthru`` methods:\n\n.. code-block:: python\n\n    import responses\n\n\n    @responses.activate\n    def test_my_api():\n        responses.add_passthru(\"https://percy.io\")\n\nThis will allow any requests matching that prefix, that is otherwise not\nregistered as a mock response, to passthru using the standard behavior.\n\nPass through endpoints can be configured with regex patterns if you\nneed to allow an entire domain or path subtree to send requests:\n\n.. code-block:: python\n\n    responses.add_passthru(re.compile(\"https://percy.io/\\\\w+\"))\n\n\nLastly, you can use the ``passthrough`` argument of the ``Response`` object\nto force a response to behave as a pass through.\n\n.. code-block:: python\n\n    # Enable passthrough for a single response\n    response = Response(\n        responses.GET,\n        \"http://example.com\",\n        body=\"not used\",\n        passthrough=True,\n    )\n    responses.add(response)\n\n    # Use PassthroughResponse\n    response = PassthroughResponse(responses.GET, \"http://example.com\")\n    responses.add(response)\n\nViewing/Modifying registered responses\n--------------------------------------\n\nRegistered responses are available as a public method of the RequestMock\ninstance. It is sometimes useful for debugging purposes to view the stack of\nregistered responses which can be accessed via ``responses.registered()``.\n\nThe ``replace`` function allows a previously registered ``response`` to be\nchanged. The method signature is identical to ``add``. ``response`` s are\nidentified using ``method`` and ``url``. Only the first matched ``response`` is\nreplaced.\n\n.. code-block:: python\n\n    import responses\n    import requests\n\n\n    @responses.activate\n    def test_replace():\n        responses.get(\"http://example.org\", json={\"data\": 1})\n        responses.replace(responses.GET, \"http://example.org\", json={\"data\": 2})\n\n        resp = requests.get(\"http://example.org\")\n\n        assert resp.json() == {\"data\": 2}\n\n\nThe ``upsert`` function allows a previously registered ``response`` to be\nchanged like ``replace``. If the response is registered, the ``upsert`` function\nwill registered it like ``add``.\n\n``remove`` takes a ``method`` and ``url`` argument and will remove **all**\nmatched responses from the registered list.\n\nFinally, ``reset`` will reset all registered responses.\n\nCoroutines and Multithreading\n-----------------------------\n\n``responses`` supports both Coroutines and Multithreading out of the box.\nNote, ``responses`` locks threading on ``RequestMock`` object allowing only\nsingle thread to access it.\n\n.. code-block:: python\n\n    async def test_async_calls():\n        @responses.activate\n        async def run():\n            responses.get(\n                \"http://twitter.com/api/1/foobar\",\n                json={\"error\": \"not found\"},\n                status=404,\n            )\n\n            resp = requests.get(\"http://twitter.com/api/1/foobar\")\n            assert resp.json() == {\"error\": \"not found\"}\n            assert responses.calls[0].request.url == \"http://twitter.com/api/1/foobar\"\n\n        await run()\n\nBETA Features\n-------------\nBelow you can find a list of BETA features. Although we will try to keep the API backwards compatible\nwith released version, we reserve the right to change these APIs before they are considered stable. Please share your feedback via\n`GitHub Issues \u003chttps://github.com/getsentry/responses/issues\u003e`_.\n\nRecord Responses to files\n^^^^^^^^^^^^^^^^^^^^^^^^^\n\nYou can perform real requests to the server and ``responses`` will automatically record the output to the\nfile. Recorded data is stored in `YAML \u003chttps://yaml.org\u003e`_ format.\n\nApply ``@responses._recorder.record(file_path=\"out.yaml\")`` decorator to any function where you perform\nrequests to record responses to ``out.yaml`` file.\n\nFollowing code\n\n.. code-block:: python\n\n    import requests\n    from responses import _recorder\n\n\n    def another():\n        rsp = requests.get(\"https://httpstat.us/500\")\n        rsp = requests.get(\"https://httpstat.us/202\")\n\n\n    @_recorder.record(file_path=\"out.yaml\")\n    def test_recorder():\n        rsp = requests.get(\"https://httpstat.us/404\")\n        rsp = requests.get(\"https://httpbin.org/status/wrong\")\n        another()\n\nwill produce next output:\n\n.. code-block:: yaml\n\n    responses:\n    - response:\n        auto_calculate_content_length: false\n        body: 404 Not Found\n        content_type: text/plain\n        method: GET\n        status: 404\n        url: https://httpstat.us/404\n    - response:\n        auto_calculate_content_length: false\n        body: Invalid status code\n        content_type: text/plain\n        method: GET\n        status: 400\n        url: https://httpbin.org/status/wrong\n    - response:\n        auto_calculate_content_length: false\n        body: 500 Internal Server Error\n        content_type: text/plain\n        method: GET\n        status: 500\n        url: https://httpstat.us/500\n    - response:\n        auto_calculate_content_length: false\n        body: 202 Accepted\n        content_type: text/plain\n        method: GET\n        status: 202\n        url: https://httpstat.us/202\n\nIf you are in the REPL, you can also activete the recorder for all following responses:\n\n.. code-block:: python\n\n    import requests\n    from responses import _recorder\n\n    _recorder.recorder.start()\n\n    requests.get(\"https://httpstat.us/500\")\n\n    _recorder.recorder.dump_to_file(\"out.yaml\")\n\n    # you can stop or reset the recorder\n    _recorder.recorder.stop()\n    _recorder.recorder.reset()\n\nReplay responses (populate registry) from files\n^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n\nYou can populate your active registry from a ``yaml`` file with recorded responses.\n(See `Record Responses to files`_ to understand how to obtain a file).\nTo do that you need to execute ``responses._add_from_file(file_path=\"out.yaml\")`` within\nan activated decorator or a context manager.\n\nThe following code example registers a ``patch`` response, then all responses present in\n``out.yaml`` file and a ``post`` response at the end.\n\n.. code-block:: python\n\n    import responses\n\n\n    @responses.activate\n    def run():\n        responses.patch(\"http://httpbin.org\")\n        responses._add_from_file(file_path=\"out.yaml\")\n        responses.post(\"http://httpbin.org/form\")\n\n\n    run()\n\n\nContributing\n------------\n\nEnvironment Configuration\n^^^^^^^^^^^^^^^^^^^^^^^^^\n\nResponses uses several linting and autoformatting utilities, so it's important that when\nsubmitting patches you use the appropriate toolchain:\n\nClone the repository:\n\n.. code-block:: shell\n\n    git clone https://github.com/getsentry/responses.git\n\nCreate an environment (e.g. with ``virtualenv``):\n\n.. code-block:: shell\n\n    virtualenv .env \u0026\u0026 source .env/bin/activate\n\nConfigure development requirements:\n\n.. code-block:: shell\n\n    make develop\n\n\nTests and Code Quality Validation\n^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n\nThe easiest way to validate your code is to run tests via ``tox``.\nCurrent ``tox`` configuration runs the same checks that are used in\nGitHub Actions CI/CD pipeline.\n\nPlease execute the following command line from the project root to validate\nyour code against:\n\n* Unit tests in all Python versions that are supported by this project\n* Type validation via ``mypy``\n* All ``pre-commit`` hooks\n\n.. code-block:: shell\n\n    tox\n\nAlternatively, you can always run a single test. See documentation below.\n\nUnit tests\n\"\"\"\"\"\"\"\"\"\"\n\nResponses uses `Pytest \u003chttps://docs.pytest.org/en/latest/\u003e`_ for\ntesting. You can run all tests by:\n\n.. code-block:: shell\n\n    tox -e py37\n    tox -e py310\n\nOR manually activate required version of Python and run\n\n.. code-block:: shell\n\n    pytest\n\nAnd run a single test by:\n\n.. code-block:: shell\n\n    pytest -k '\u003ctest_function_name\u003e'\n\nType Validation\n\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\n\nTo verify ``type`` compliance, run `mypy \u003chttps://github.com/python/mypy\u003e`_ linter:\n\n.. code-block:: shell\n\n    tox -e mypy\n\nOR\n\n.. code-block:: shell\n\n    mypy --config-file=./mypy.ini -p responses\n\nCode Quality and Style\n\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\"\n\nTo check code style and reformat it run:\n\n.. code-block:: shell\n\n    tox -e precom\n\nOR\n\n.. code-block:: shell\n\n    pre-commit run --all-files\n","funding_links":["https://sentry.io/pricing/","https://sentry.io/"],"categories":["Testing","Python","资源列表","Programming","测试","Web Testing","File Manipulation","Testing [🔝](#readme)","Mock and Stub","Awesome Python"],"sub_categories":["测试","Mock","HTTP Clients","Testing"],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fgetsentry%2Fresponses","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fgetsentry%2Fresponses","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fgetsentry%2Fresponses/lists"}