#11942: testing from a checkout is overly complicated
----------------------------------------+-----------------------------------
Reporter: termie | Owner: nobody
Status: closed | Milestone:
Component: Testing framework | Version: SVN
Resolution: duplicate | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
----------------------------------------+-----------------------------------
Changes (by russellm):
* status: new => closed
* needs_better_patch: => 0
* resolution: => duplicate
* needs_tests: => 0
* needs_docs: => 0
Comment:
This is an exact duplicate of #6298.
I'm _deeply_ opposed to assumed defaults, because there's no such thing.
When you run the test system, it isn't enough to just run it for SQLite -
you need to run it for _all_ databases. I appreciate that this isn't
always possible for first-time users, but I want people to be
_consciously_ made aware of the fact that they are running the test suite
for a _specific_ configuration.
--
Ticket URL: <http://code.djangoproject.com/ticket/11942#comment:1>
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 [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
