Hi Shai,
The discover runner does discovery based on pattern.
So, if your tests are named, test_*.py, they would by be discovered by
default. Test discovery is recursive, under the root, so it doesn't
matter if you have tests in a tests directory.
The __init__.py imports would be redundant, and
Hi,
+1 in general. One concern, and one idea:
>
> -- Backwards-incompatible changes --
>
> * Some valid test structures in Django don't work with unittest2. For
> instance, tests in `tests/__init__.py` don't match a patter than
> unittest would recognize if running discovery on a module.
>
I
+1, in general.
>> ** The current "myapp." notation is not part of unittest2, and
>> would go away
I don't know of anyone for whom this would represent a breakage in deployment
processes, since it's usually used for quick local testing only.
One concern, however:
How will `django-admin.py te
Hi all,
There are some important design decisions to be made if we include
unittest2 discovery into Django.
This message documents a proposed API, the pros and cons, and
decisions that need to be made.
https://code.djangoproject.com/ticket/17365
-- Limitation of current test setup: --
* Tests
