#20918: Tidy up implementation of custom assertions
--------------------------------------+--------------------
Reporter: mjtamlyn | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Testing framework | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+--------------------
The custom assertions provided by Django have a significant amount of
duplication between the true and false cases - e.g. between
`assertContains` and `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.
For example, `assertNotContains` seems to not handle streaming responses.
--
Ticket URL: <https://code.djangoproject.com/ticket/20918>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/051.d9e93e3bfd8bca559bf2278b0c538d7d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
