Improve documentation on how to run tests #131

Closed
bthirion opened this Issue Feb 9, 2012 · 3 comments

Comments

Projects
None yet
3 participants
@bthirion
Contributor

bthirion commented Feb 9, 2012

I don't understand this error. Is this related to a nosetest version issue ?

nosetests --with-doctest
...

ERROR: Failure: ValueError (line 46 of the doctest for nipy.algorithms.statistics.models.regression.OLSModel has an invalid option: '+FP_6DP')

...

ERROR: Failure: ValueError (line 14 of the doctest for nipy.algorithms.statistics.formula.formulae.RandomEffects has an invalid option: '+IGNORE_OUTPUT')

...

ERROR: Failure: ValueError (line 22 of the doctest for nipy.modalities.fmri.utils.define has an invalid option: '+SYMPY_EQUAL')

@matthew-brett

This comment has been minimized.

Show comment Hide comment
@matthew-brett

matthew-brett Feb 12, 2012

Member

nipy has some custom doctest machinery implementing these directives (IGNORE_OUTPUT, FP_6DP, SYMPY_EQUAL).

nosetests needs custom extensions to run these tests, so the raw nosetests command will fail these tests as you've seen.

To pick up the extensions, use the nipy.test() or the tools/nipnost script, which is shell around nosetests, but loading the extensions.

Member

matthew-brett commented Feb 12, 2012

nipy has some custom doctest machinery implementing these directives (IGNORE_OUTPUT, FP_6DP, SYMPY_EQUAL).

nosetests needs custom extensions to run these tests, so the raw nosetests command will fail these tests as you've seen.

To pick up the extensions, use the nipy.test() or the tools/nipnost script, which is shell around nosetests, but loading the extensions.

@yarikoptic

This comment has been minimized.

Show comment Hide comment
@yarikoptic

yarikoptic Apr 25, 2012

Member

should this issue be kept open (then retitled to smth like "wishlist: nose extension to run tests with nosetests") or closed (since now there should be no such failure if tests are ran in a documented way)

Member

yarikoptic commented Apr 25, 2012

should this issue be kept open (then retitled to smth like "wishlist: nose extension to run tests with nosetests") or closed (since now there should be no such failure if tests are ran in a documented way)

@matthew-brett

This comment has been minimized.

Show comment Hide comment
@matthew-brett

matthew-brett Apr 25, 2012

Member

On Wed, Apr 25, 2012 at 9:06 AM, Yaroslav Halchenko
reply@reply.github.com
wrote:

should this issue be kept open (then retitled to smth like "wishlist: nose extension to run tests with nosetests") or closed (since now there should be no such failure if tests are ran in a documented way)


Reply to this email directly or view it on GitHub:
#131 (comment)

Closed I think; although maybe running the tests should be better and
more clearly documented.

Member

matthew-brett commented Apr 25, 2012

On Wed, Apr 25, 2012 at 9:06 AM, Yaroslav Halchenko
reply@reply.github.com
wrote:

should this issue be kept open (then retitled to smth like "wishlist: nose extension to run tests with nosetests") or closed (since now there should be no such failure if tests are ran in a documented way)


Reply to this email directly or view it on GitHub:
#131 (comment)

Closed I think; although maybe running the tests should be better and
more clearly documented.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment