#15582 closed Bug (fixed)
Docs don't mention that TestCase.multi_db affects test fixtures
| Reported by: | Paul Winkler | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | 1.2 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
From reading http://docs.djangoproject.com/en/1.2/topics/testing/#django.test.TestCase.fixtures
I wouldn't guess that you have to do anything special to load fixtures in multi-database setups.
And http://docs.djangoproject.com/en/1.2/topics/testing/#django.test.TestCase.multi_db
says nothing about fixtures. A strict reading would make me think multi_db only affects cleaning databases and maybe loading initial_data fixtures; it doesn't say that it affects loading the fixtures from TestCase.fixtures.
Perhaps that's implied, but I think it should be explicit.
This is especially confusing because there is no output from the test runner at all about fixture loading, either success or failure.
Attachments (1)
Change History (9)
comment:1 by , 16 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
comment:2 by , 16 years ago
| Type: | → Bug |
|---|
comment:3 by , 16 years ago
| Severity: | → Normal |
|---|
comment:4 by , 15 years ago
| UI/UX: | unset |
|---|
by , 13 years ago
| Attachment: | 15582.diff added |
|---|
comment:6 by , 13 years ago
| Has patch: | set |
|---|
comment:7 by , 13 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Change UI/UX from NULL to False.