#7835: Provide the ability for model definitions that are only availably during
testing
----------------------------------------+-----------------------------------
Reporter: russellm | Owner: kkubasik
Status: new | Milestone:
Component: Testing framework | Version: SVN
Resolution: | Keywords: feature test models
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
----------------------------------------+-----------------------------------
Comment (by russellm):
@carljm; you're right that it hasn't been mentioned, but it hasn't been
neglected, either.
To my mind, there are (a least) three features missing from the "put
models in tests.py" technique:
* Specify only specific models for a specific test (e.g., only have the
Article model for this particular test)
* Cleanup of contenttypes, permissions -- and most importantly -- the app
cache itself.
* Defining multiple test apps. For example, to test the admin, you need
multiple apps to demonstrate the app index works.
My original motivation here was to provide a test environment that was
rich enough to support tests for model migrations. For that, you need all
three features.
--
Ticket URL: <http://code.djangoproject.com/ticket/7835#comment:27>
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-updates@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.
