Opened 15 years ago
Closed 14 years ago
#11241 closed New feature (duplicate)
Allow assertFormError to check a formsets' non_form_errors
| Reported by: | Seth Buntin | Owned by: | nobody |
|---|---|---|---|
| Component: | Testing framework | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | sethtrain@… | Triage Stage: | Accepted |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
When using assertFormError while testing a formset it would be nice to be able assert with a formsets' non_form_errors, I have changed the assertFormError to handle this case.
Attachments (1)
Change History (5)
by , 15 years ago
| Attachment: | assertFormError.diff added |
|---|
comment:1 by , 15 years ago
| milestone: | 1.1 |
|---|---|
| Triage Stage: | Unreviewed → Accepted |
comment:2 by , 15 years ago
Unless I am misunderstanding how one might use assertFormError to test a formset, I would suggest that a seperate function is required to test formset field-errors and non-field-errors. This would seem a more natural place to test for non-form errors. I have proposed such a solution in ticket:11603.
comment:3 by , 14 years ago
| Severity: | → Normal |
|---|---|
| Type: | → New feature |
comment:4 by , 14 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
Closing in favour of #11603, which addresses a larger scope and has a more comprehensive patch.
Note:
See TracTickets
for help on using tickets.
Idea seems sound, but the deadline for v1.1 features has passed.