link to shining panda

Issue #228 new
Thomas Waldmann
created an issue

... would be nice to have.

aside from helping to ensure code correctness (check results), it would also help to avoid simple NameErrors/AttributeErrors that can easily creep in when code has no complete test coverage - then those errors are often found by users in production.

related to this is the question whether doctests scale to such good coverage or whether separate tests would be better.

for separate tests, I'ld recommend using pytest, which is a nice framework (and you have to type less than with the usual unittest stuff).

Comments (4)

  1. Thomas Waldmann reporter

    apropos, about coverage: do we want some tool that shows how good the test coverage is? would be maybe helpful to at least make sure all code is run by the tests, to avoid such stuff as in #268 .

  2. Log in to comment