#17365: Add optional unittest2 discovery test suite runner
-------------------------------------+-------------------------------------
Reporter: jezdez | Owner: nobody
Type: New feature | Status: new
Component: Testing framework | Version: SVN
Severity: Normal | Resolution:
Keywords: | Triage Stage: Design
Has patch: 0 | decision needed
Needs tests: 0 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by carljm):
Summary of discussion with Jacob on IRC:
- There's no reason for Django to ship two test runners, and test
discovery doesn't bite in production, so the back-compat bar is lower. We
should just do what we think is right and document the changes well.
- Ignoring tests in `models.py` is fine, that's ugly and nobody should be
doing it anyway (we do it 36 times in our own test suite, so we'd need to
fix that).
- There should be a way to a) discover tests in all `INSTALLED_APPS`, b)
discover tests in a single app, c) discover tests under an arbitrary
supplied root path, and d) discover tests rooted in the current directory.
These could all be done with flags to `manage.py test`; e.g. `manage.py
test` discovers based in `.`, `--installed` flag does all installed apps,
`--app=app` for a single app, `--root=some/path`, etc. It would be ok to
change the default from "all installed apps" to "discovery based in CWD",
if it's easy for people to get back to "all installed apps" with a flag.
Aymeric also suggested a `TEST_APPS` setting defaulting to
`INSTALLED_APPS`, to set the default set of apps to discover tests in.
This is something I've seen a lot of projects in the wild do.
--
Ticket URL: <https://code.djangoproject.com/ticket/17365#comment:9>
Django <https://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.
