That seems very complicated, All I did was put this in tests/__init__.py
from myproj.tests.model_tests import *
from myproj.tests.view_tests import *
(etc)
2008/5/23 Sebastian Noack <[EMAIL PROTECTED]>:
> On Fri, 23 May 2008 13:32:45 -0500
> "Gary Wilson Jr." <[EMAIL PROTECTED]> wrote:
>> In c
On Fri, 23 May 2008 13:32:45 -0500
"Gary Wilson Jr." <[EMAIL PROTECTED]> wrote:
> In case you haven't figured this out already, it can be done by
> importing your unit test classes from the test/*.py modules in
> tests/__init__.py
That is exactly what I have done at my work, just a few days ago.
Alex Koshelev wrote:
> No. Not `tests.py`, but `tests` module - that can be a package of many
> other modules/files
In case you haven't figured this out already, it can be done by
importing your unit test classes from the test/*.py modules in
tests/__init__.py
Gary
--~--~-~--~~---
No. Not `tests.py`, but `tests` module - that can be a package of many
other modules/files
On May 7, 12:21 am, Steve <[EMAIL PROTECTED]> wrote:
> Hi, we're just getting started using Django unit tests, and it looks
> like the documentation says you can only have unit tests in two files:
> models.
Hi,
you can always define your own test runner which will look not only in
tests and models, but in every module.
This question is more suited for the django-users mailing list, this
list is intended for discussing development of django internals.
On Tue, May 6, 2008 at 10:21 PM, Steve <[EMAIL PR
Hi, we're just getting started using Django unit tests, and it looks
like the documentation says you can only have unit tests in two files:
models.py and tests.py. We would prefer to put our unit tests in many
different files, with, say, each main-line .py file having a
corresponding unit-test fi
