On Wed, Feb 18, 2009 at 11:43 AM, James Evans <jreva...@earthlink.net> wrote:
> All,
>
> I have just submitted a first-cut at a unit-test harness. The unit-tests do
> require the use of the 'nose' python module.
[...]
> Any questions or comments?
This is great, many thanks! I'd just suggest, if possible, adding a
top-level .test() function, so that the usual idiom for package
testing 'import foo;foo.test()' can be applied. I have a shell
function for that:
function pytest {
# Run the test suite for a python package by name.
# This assumes the package has a top-level .test() routine to run its
# test suite.
local pname=$1
python -c "import $pname;${pname}.test()"
}
that I use for things like testing numpy or scipy easily:
uqbar[~]> pytest numpy
Running unit tests for numpy
[...]
----------------------------------------------------------------------
Ran 1931 tests in 4.999s
OK (KNOWNFAIL=1, SKIP=11)
Cheers,
f
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
