You’re absolutely on the right track – the breaking test in that case is certainly due to Django’s change in
PUT behavior for the test client.
Your fix looks right to me, too. 415 is the “Unsupported Media Type” response, which means that the request content type wasn’t something that could be handled by any of the parsers configured for the view.
Normally in case like this, that’d be due to forgetting to set the content type of the request, but it looks like you’ve got that correctly set to
Things to double check:
- Exactly what does
response.datadisplay as the error details?
- What do you have configured in you
DEFAULT_PARSER_CLASSESsetting, if you have one, or what do you have set on the view attribute
parser_classesif it has one?
- Make sure there’s not a typo in
content_typein the test (even though it’s correct here).
Thanks for your comments – that clears everything up. You’ve only got the JSON parser installed, but you’re trying to send Form encoded data. You should either:
MultiPartParserto your settings/view, so that it supports form encodings. (Note also that the default
DEFAULT_PARSER_CLASSESsetting does include them, so if you don’t set anything at all it’ll work as expected)
- Encode the request using
jsonencoding, not form encoding…
data=json.dumps(prepare_dict(self.account)), content_type="application/json"in your test case.