[Python-checkins] devguide: Clarify what fields to set in the tracker when filing a coverage increase patch.
brett.cannon
python-checkins at python.org
Tue Jan 18 04:34:49 CET 2011
brett.cannon pushed f1b9f476cfe0 to devguide:
http://hg.python.org/devguide/rev/f1b9f476cfe0
changeset: 118:f1b9f476cfe0
tag: tip
user: Brett Cannon <brett at python.org>
date: Mon Jan 17 19:34:35 2011 -0800
summary:
Clarify what fields to set in the tracker when filing a coverage increase patch.
files:
coverage.rst
diff --git a/coverage.rst b/coverage.rst
--- a/coverage.rst
+++ b/coverage.rst
@@ -36,6 +36,9 @@
have an accurate, up-to-date notion of what modules need the most work.
+Measuring Coverage
+""""""""""""""""""
+
Using coverage.py
-----------------
@@ -136,3 +139,13 @@
Once the tests are done you will find the directory you specified contains
files for each executed module along with which lines were executed how many
times.
+
+
+Filing the Issue
+""""""""""""""""
+Once you have increased coverage, you need to
+:ref:`generate the patch <patch>`, submit it to the `issue tracker`_. For the
+issue set the Components to "Test" and Versions to the version of Python you
+worked on (i.e., the in-development version).
+
+.. _issue tracker: http://bugs.python.org
--
Repository URL: http://hg.python.org/devguide
More information about the Python-checkins
mailing list