RetroSearch Browse

Mon Mar 4 21:07:15 CET 2013 · https://mail.python.org/pipermail/python-dev/2013-March/124558.html

On 5 March 2013 05:51, Barry Warsaw <barry at python.org> wrote:
> I should have added "from the command line".  E.g. is it:
>
> $ python -m unittest discover
> $ python setup.py test
> $ python setup.py nosetests
> $ python -m nose test
> $ nosetests-X.Y

$ testr run

:)

> Besides having a multitude of choices, there's almost no way to automatically
> discover (e.g. by metadata inspection or some such) how to invoke the tests.
> You're often lucky if there's a README.test and it's still accurate.

<pimping own horse>
If there is a .testr.conf you can run 'testr init; testr run'. Thats
the defined entry point for testr, and .testr.conf can specify running
make, or setup.py build or whatever else is needed to run tests.
</pimp>

I would love to see a declaritive interface so that you can tell that
is what you should run.

-Rob

-- 
Robert Collins <rbtcollins at hp.com>
Distinguished Technologist
HP Cloud Services

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2013-March/124558.html below:

[Python-Dev] Python Language Summit at PyCon: Agenda