NumPy has recently switched to using nosetest for their testing framework:

http://www.somethingaboutorange.com/mrl/projects/nose/

Basically, it is unittest on steroids (and uses/operates together with
unittest). The major features:
- Out of the box unit test discovery on a source tree (according to some
configurable name pattern on packages and modules)
- The ability to make simple functions etc. test cases if they have the
right name. Though unittest classes are of course supported as well.
- One can write multiple tests in one function, then "yield" each one of
them, and each will be a seperate test case in the reports.

I just wouldn't like to have rewrite discovery of unittests in runtests.py
when this is already there in nosetests.

What do you think -- will it be bad to have this as a dependency?

Dag Sverre


_______________________________________________
Cython-dev mailing list
[email protected]
http://codespeak.net/mailman/listinfo/cython-dev

Reply via email to