Re: Overview of ETS 3.0 tests

Yes, I agree.  Using the tests option in setup.cfg things work with
both nose 0.9.3 and 0.10.3, however now if somebody adds new tests,
the list needs to be updated.  I think I will try to use the standard
setup.cfg approach when possible, and only fall back on test_all.py
when things need a more specific solution.

Robert Kern wrote:
> On Sat, Jul 19, 2008 at 17:14, Ilan Schnell <ischnell@...> wrote:
>   
>> Thanks Robert, this is important for me to know.  This means that
>> test_all.py
>> should not run anything in integrationtests either.
>>     
>
> Yes. However, I do recommend using the setup.cfg approach instead of
> test_all.py. It allows users to just run nosetests with whatever
> commandline options they need (e.g. --pdb, --with-coverage, etc.).
>
>