#23620: Use more specific assertions than assertTrue in tests
-------------------------------------+-------------------------------------
Reporter: timgraham | Owner:
Type: | averybigant
Cleanup/optimization | Status: assigned
Component: Uncategorized | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by berkerpeksag):
https://github.com/django/django/pull/3432
Should I create a new ticket for `assertFalse(a == b)`, `assertFalse(a !=
b)`, `assertFalse("foo" in a)` etc. instances?
--
Ticket URL: <https://code.djangoproject.com/ticket/23620#comment:3>
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/067.be1c1b63a7c710f3a8935c9044c907f7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
