Tidy up implementation of custom assertions
|Reported by:||Marc Tamlyn||Owned by:||nobody|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
The custom assertions provided by Django have a significant amount of duplication between the true and false cases - e.g. between
assertNotContains. There appear to be subtle difference and it concerns me that perhaps some of these are bugfixes which have only been applied to one of the methods.
assertNotContains seems to not handle streaming responses.