Update Documentation for "Testing Responses" section on Django Documentation

[AvuGradConnection]

​https://docs.djangoproject.com/en/2.2/topics/testing/tools/#testing-responses

Under the Testing Responses section of this page, it is detailed to the user how to interact with the "Response" object returned from the client request. There is an assumption made that the response will be a 'django.http.response.HttpResponse' (HttpResponse) whereas the endpoint responsible for returning the response may/may not return a response object that is an HttpResponse, or even a response like object at all.

Users should be made aware of this and the fact that the interface described for communicating with the response might be significantly different depending on what type of response the view handling the response returns. This may or may not be a response like object. The user should be made aware that if they are using any other mechanism besides Django default views to return response objects then the response may differ significantly from the the documentation interface explained.

Example: Django Rest Framework, manipulates(sub classes) the HttpResponse in providing their "ApiViews" and this response object works slightly differently from the class HttpResponse object described in the documentation.

[Carlton Gibson]

Hi, thanks for the report.

The section in question is explicitly discussing responses returned by the Django test Client. Even if you're using DRF, it's still an HttpResponse.
I think that assumption is reasonable.

​DRF has its own testing docs that explain the additions made there.
That's the right place for that addition.