Message 268709 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	shoshber
Recipients	shoshber
Date	2016-06-17.05:35:08
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1466141708.88.0.0388300458163.issue27341@psf.upfronthosting.co.za>
In-reply-to

Content
(at least in my case) I committed two tests before I realized the tests were not being run: https://github.com/nipy/nipype/blob/abe7920a051f1570ccce4b71f26f50102d6e4e12/nipype/testing/tests/test_utils.py#L23 I realized this afternoon, while writing some more tests, that tests with the patch decorator were all reported as "OK", even when I wanted them to fail. Turns out they aren't being run at all. I commented out all the yield statements, and the tests ran just as they should. I don't know exactly what is going on here, but might raising an error or warning be good here? Originally filed here: https://github.com/testing-cabal/mock/issues/366

(at least in my case)

I committed two tests before I realized the tests were not being run: https://github.com/nipy/nipype/blob/abe7920a051f1570ccce4b71f26f50102d6e4e12/nipype/testing/tests/test_utils.py#L23

I realized this afternoon, while writing some more tests, that tests with the patch decorator were all reported as "OK", even when I wanted them to fail. Turns out they aren't being run at all.

I commented out all the yield statements, and the tests ran just as they should.

I don't know exactly what is going on here, but might raising an error or warning be good here?

Originally filed here: https://github.com/testing-cabal/mock/issues/366

History
Date	User	Action	Args
2016-06-17 05:35:08	shoshber	set	recipients: + shoshber
2016-06-17 05:35:08	shoshber	set	messageid: <1466141708.88.0.0388300458163.issue27341@psf.upfronthosting.co.za>
2016-06-17 05:35:08	shoshber	link	issue27341 messages
2016-06-17 05:35:08	shoshber	create