testing policy document recommends the wrong group of assert* methods
[email protected] Sun, 10 Jan 2010 23:04:28 -0000
| Newsgroups | gmane.comp.python.twisted.bugs |
|---|---|
| Message-ID | <[email protected]> |
New submission from exarkun <[email protected]>: In #2631 we added a recommendation that `assertEqual` be preferred in Twisted tests, over `assertEquals`. This is the opposite of the conclusion I remember the group coming to (although I only remember a count of existing uses as the basis for this decision). Am I mis-remembering? Do we really prefer `assertEqual` now? I don't think so. We should fix the document to reflect reality. ---------- Type : defect Component: core Keywords : documentation Priority : normal Nosy : glyph, radix, itamarst ---------- http://twistedmatrix.com/trac/ticket/4204