#36280: Replace cm.exception.messages with assertRaisesMessage() in tests
--------------------------------------+------------------------------------
Reporter: Tim Graham | Owner: (none)
Type: Cleanup/optimization | Status: new
Component: Core (Other) | Version: dev
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 aloony):
Replying to [comment:1 Sarah Boyce]:
> Agree that most can be updated
> Likely that the ones that check the error code (`cm.exception.code`) may
need to stay the same
I assume the same goes for assertEqual's that validate two lists of
errors? Since, assertRaisesMessage validates against a string, not a list
of them. Otherwise, we would need to write a new assert for that
specifically.
--
Ticket URL: <https://code.djangoproject.com/ticket/36280#comment:2>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070195e1bfd738-54b47382-da23-49d2-9681-9229441431c8-000000%40eu-central-1.amazonses.com.
