[Python-checkins] devguide: Mention that coverage should always be run for a module in isolation to get a

[brett.cannon]

brett.cannon pushed dfa3335be30d to devguide:

http://hg.python.org/devguide/rev/dfa3335be30d
changeset:   219:dfa3335be30d
tag:         tip
user:        Brett Cannon <brett at python.org>
date:        Fri Jan 28 16:00:24 2011 -0800
summary:
  Mention that coverage should always be run for a module in isolation to get a more accurate measurement of the effectiveness of the module's tests.

files:
  coverage.rst

diff --git a/coverage.rst b/coverage.rst
--- a/coverage.rst
+++ b/coverage.rst
@@ -36,6 +36,11 @@
 takes some time to complete, but you will
 have an accurate, up-to-date notion of what modules need the most work.
 
+Do make sure, though, that for any module you do decide to work that you run
+coverage for just that module. This wll make sure you know how good the
+explicit coverage of the module is from its own set of tests instead of from
+implicit testing by other code that happens to use the module.
+
 
 Measuring Coverage
 """"""""""""""""""

--
Repository URL: http://hg.python.org/devguide