On Jun 10, 2010, at 10:34 PM, John H Palmieri wrote:
On Jun 10, 9:47 pm, Andrey Novoseltsev <novos...@gmail.com> wrote:
On Jun 10, 9:41 pm, Jason Grout <jason-s...@creativetrax.com> wrote:
I imagine that after doctest coverage is up to 100% function
coverage that there will be a new push to then get the statement
coverage up to 100%. It would be interesting even now to see how
much
statement coverage lagged behind function coverage.
Where should such tests go?
They can go in separate files, files which, for example, are not
included in the reference manual. The file sage/homology/tests.py is
an example. Each function should have doctests (so the goal is still
100% coverage), but it's not a big deal to relegate lots of technical
test to less visible places.
Personally, I would much rather put the relevant tests locally right
in the docstring and hide them from the documentation generators.
Especially as TESTS blocks often test corner cases or other
technicalities relevant to that specific function.
- Robert
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
