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 michael.foord
Recipients brett.cannon, ezio.melotti, michael.foord, rhettinger, serhiy.storchaka
Date 2019-03-31.01:15:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1553994902.4.0.887414775341.issue36485@roundup.psfhosted.org>
In-reply-to
Content
Tests codify knowledge about the system under test, so it doesn't matter that the test suite has to know how to clear caches. It's specifically a good thing that the test writer knows which caches exist and need clearing, and how to do it. The harder thing mighty be determining what scope to do the clearing (per test, class or module) bit unittest exposes hooks for fixtures at those points for anything that needs doing automatically.
History
Date User Action Args
2019-03-31 01:15:02michael.foordsetrecipients: + michael.foord, brett.cannon, rhettinger, ezio.melotti, serhiy.storchaka
2019-03-31 01:15:02michael.foordsetmessageid: <1553994902.4.0.887414775341.issue36485@roundup.psfhosted.org>
2019-03-31 01:15:02michael.foordlinkissue36485 messages
2019-03-31 01:15:01michael.foordcreate