#14296: 'manage.py test' failing for apps that access read-only databases
----------------------------------------+-----------------------------------
Reporter: kthhrv | Owner: nobody
Status: new | Milestone:
Component: Testing framework | Version: 1.2
Resolution: | Keywords:
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
----------------------------------------+-----------------------------------
Changes (by russellm):
* stage: Unreviewed => Accepted
Comment:
This sort of thing makes my teeth itch, because it's *really* bad testing
practice -- tests should be repeatable, and anything with live data, by
definition, isn't guaranteed repeatable.
A more interesting, but related use case is when you don't have permission
to create or destroy databases, but you do have access to a database that
you can use for testing purposes. Since solving this use case essentially
implies solving the use case for this ticket, I'll mark this accepted.
--
Ticket URL: <http://code.djangoproject.com/ticket/14296#comment:4>
Django <http://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 post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
