Message156757
| Author |
michael.foord |
| Recipients |
gwrtheyrn, michael.foord, pitrou, tshepang |
| Date |
2012年03月25日.13:14:07 |
| SpamBayes Score |
1.2823519e-05 |
| Marked as misclassified |
No |
| Message-id |
<1332681247.82.0.766577758267.issue14403@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
The opposite of calling assertRaises is simply calling the code. A comment as to why you're calling the code is sufficient documentation as to the intent of the test.
In general the difference be a test failure and error is not useful - you *still* have to look at the traceback (failure details) to see *why* the test failed / errored. I'm sure the distinction comes from JUnit that unittest was originally based on (and yes - overengineered for Python). |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2012年03月25日 13:14:07 | michael.foord | set | recipients:
+ michael.foord, pitrou, tshepang, gwrtheyrn |
| 2012年03月25日 13:14:07 | michael.foord | set | messageid: <1332681247.82.0.766577758267.issue14403@psf.upfronthosting.co.za> |
| 2012年03月25日 13:14:07 | michael.foord | link | issue14403 messages |
| 2012年03月25日 13:14:07 | michael.foord | create |
|