Re: django test-runner annoyances

2011-09-15 Thread mvr
On Sep 14, 4:16 pm, Carl Meyer wrote: > > I'm generally in favor of updating Django's test runner to be more > consistent with what the rest of the Python testing world does. Being > able to reference test files, suites, and tests by > fully-qualified-dotted-path rather than

Re: django test-runner annoyances

2011-09-15 Thread Filip Dupanović
Like Carl and Travis said, Django's test runner supports the notion that a Django app has all it's test cases collected in the `models` and `tests` module. Most of the time, If your app's `tests` module gets too crowded, fracturing the app into smaller apps works. However, if you have to go

Re: django test-runner annoyances

2011-09-14 Thread Travis Swicegood
Hello; I second all of what Carl said and would like to point out the app-refactor. I believe the most current code still lives in the app-loading branch on jezdez's repository on GitHub[1]. The reason I point this out is because the current testing structure is a legacy of the way Django

Re: django test-runner annoyances

2011-09-14 Thread Carl Meyer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/13/2011 08:46 AM, mvr wrote: > Why doesn't the django test management command / test builder allow > fully-qualified package names instead of just app-relative ones? > > At work we've been using the method below to monkey-patch the test >

django test-runner annoyances

2011-09-13 Thread mvr
Why doesn't the django test management command / test builder allow fully-qualified package names instead of just app-relative ones? At work we've been using the method below to monkey-patch the test builder, so that $ django-admin.py test my_module.my_app.tests.some_test_file always works as