On 5 March 2013 05:51, Barry Warsaw firstname.lastname@example.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.