Opened 13 years ago
Closed 13 years ago
#18008 closed Bug (wontfix)
[patch] for broken test: test_loaddata_error_message
Reported by: | hoffmaje | Owned by: | hoffmaje |
---|---|---|---|
Component: | Core (Management commands) | Version: | dev |
Severity: | Normal | Keywords: | unittest test IntegrityError assertRaises |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
The attached diff fixes a broken test in tests/modeltests/fixtures/tests. call_command raises IntegrityError, that was not catched with assertRaises.
Attachments (1)
Change History (7)
by , 13 years ago
Attachment: | modeltests_fixtures_tests.diff added |
---|
comment:1 by , 13 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:2 by , 13 years ago
Version: | 1.4 → SVN |
---|
comment:3 by , 13 years ago
Summary: | Fix broken test: test_loaddata_error_message → [patch] for broken test: test_loaddata_error_message |
---|
comment:4 by , 13 years ago
comment:5 by , 13 years ago
My fault, sorry, forgot to undo a todays morning trial to ease exception handling in loaddata.
comment:6 by , 13 years ago
Resolution: | → wontfix |
---|---|
Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
Please explain a little more why you think the current test is broken. Note that nobody has reported the test to fail, neither the CI servers (http://ci.djangoproject.com/). The loaddata command is currently catching all exceptions, so how are you able to intercept the IntegrityError in the test?