remove BaseRequest and BaseResponse
This commit is contained in:
parent
fdba0d2526
commit
1936ca8a2e
5 changed files with 5 additions and 5 deletions
|
|
@ -119,7 +119,7 @@ Notice that our test functions begin with the word `test`; this allows
|
|||
By using ``client.get`` we can send an HTTP ``GET`` request to the
|
||||
application with the given path. The return value will be a
|
||||
:class:`~flask.Flask.response_class` object. We can now use the
|
||||
:attr:`~werkzeug.wrappers.BaseResponse.data` attribute to inspect
|
||||
:attr:`~werkzeug.wrappers.Response.data` attribute to inspect
|
||||
the return value (as string) from the application.
|
||||
In this case, we ensure that ``'No entries here so far'``
|
||||
is part of the output.
|
||||
|
|
|
|||
|
|
@ -302,7 +302,7 @@ URL when the register view redirects to the login view.
|
|||
:attr:`~Response.data` contains the body of the response as bytes. If
|
||||
you expect a certain value to render on the page, check that it's in
|
||||
``data``. Bytes must be compared to bytes. If you want to compare text,
|
||||
use :meth:`get_data(as_text=True) <werkzeug.wrappers.BaseResponse.get_data>`
|
||||
use :meth:`get_data(as_text=True) <werkzeug.wrappers.Response.get_data>`
|
||||
instead.
|
||||
|
||||
``pytest.mark.parametrize`` tells Pytest to run the same test function
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue