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 pitrou
Recipients gwrtheyrn, michael.foord, pitrou, tshepang
Date 2012-03-25.12:14:38
SpamBayes Score 3.6051165e-06
Marked as misclassified No
Message-id <1332677389.3335.0.camel@localhost.localdomain>
In-reply-to <1332677149.69.0.0562835064624.issue14403@psf.upfronthosting.co.za>
Content
> >> I don't want to simply execute the code and hope that it doesn't raise 
> >> an exception, because if it does, the test fails with an "error" status 
> >> instead of a "failed" status.
> > 
> > So what?
> 
> A buggy test is not the same thing as a test that fails because the
> test result did not meet your assertions.

That's a completely meaningless difference in my experience. Raising an
exception usually means the tested code is buggy, not the test.
Whoever introduced this distinction probably overengineered it.
History
Date User Action Args
2012-03-25 12:14:39pitrousetrecipients: + pitrou, michael.foord, tshepang, gwrtheyrn
2012-03-25 12:14:38pitroulinkissue14403 messages
2012-03-25 12:14:38pitroucreate