[Numpy-discussion] Going toward time-based release ?
Stéfan van der Walt
Tue May 13 08:02:52 CDT 2008
2008/5/13 Matthieu Brucher <firstname.lastname@example.org>:
> > As for the NumPy unit tests: I have placed coverage reports online
> > (http://mentat.za.net/numpy/coverage). This only covers Python (not
> > extension) code, but having that part 100% tested is not impossible,
> > nor would it take that much effort. The much more important issue is
> > having the C extensions tested, and if anyone can figure out a way to
> > get gcov to generate those coverage reports, I'd be in the seventh
> > heaven. Thus far, the only way I know of is to build one large,
> > static Python binary that includes numpy.
> I tried something similar with figleaf on my own code, but it seems that
> every test that is decorated with @raises is not tested. Does your coverage
> include these tests ? I didn't change much of your script to do it.
> I tried the pinocchio nose extension as well, but it seems it is not
> compatible with figleaf anymore :| (there is a thread on the testing ML, but
> no answers so far :|)
I don't know about the "@raises" parameter. Those aren't used in
NumPy at the moment. I also don't know which mechanism figleaf uses
to track coverage, but if you investigte the issue further, please
keep us up to date.
More information about the Numpy-discussion