Message326531
| Author |
serhiy.storchaka |
| Recipients |
axitkhurana, barry, dablanc, ezio.melotti, michael.foord, r.david.murray, rbcollins, serhiy.storchaka, vajrasky |
| Date |
2018年09月27日.08:01:06 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1538035266.91.0.545547206417.issue24412@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
There is a design issue with the order of cleaning up. tearDown() is purposed to release resources acquired in setUp(). Resources acquired in test methods will be released in doCleanup() if use addCleanup(), but since doCleanup() is called after tearDown(), resources will be released not in reversed order of the time of acquiring. This causes issues if resources acquired in a test method depends on the resource acquired in setUp().
Adding doClassCleanups() and doModuleCleanups() with the same semantic will introduce this problem at class and module level. |
|