#33348: Change API of assertFormError to take an actual form object
-------------------------------------+-------------------------------------
Reporter: Baptiste Mispelon | Owner: Baptiste
Type: | Mispelon
Cleanup/optimization | Status: closed
Component: Testing framework | Version: dev
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"50e1e7ef8ef63271717f8bcab76d7151ccf4bb18" 50e1e7ef]:
{{{
#!CommitTicketReference repository=""
revision="50e1e7ef8ef63271717f8bcab76d7151ccf4bb18"
Fixed #33348 -- Changed
SimpleTestCase.assertFormError()/assertFormsetErrors() to take
form/formset.
Instead of taking a response object and a context name for
the form/formset, the two methods now take the object directly.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/33348#comment:13>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/0107017ffd9a3c05-c99ce9ef-27ea-479f-9be7-a70a04887c01-000000%40eu-central-1.amazonses.com.
