diff options
| author | Ned Batchelder <ned@nedbatchelder.com> | 2016-01-16 11:36:08 -0500 |
|---|---|---|
| committer | Ned Batchelder <ned@nedbatchelder.com> | 2016-01-16 11:36:08 -0500 |
| commit | 360c7725d4a82e5ad7b9ebc2e9aa459b39f5c2b4 (patch) | |
| tree | 5786173d288370a16458159982fe56707d99ed68 /doc/branch.rst | |
| parent | 24682d3cecd834229fde6e4e09d4380359e3a49a (diff) | |
| download | python-coveragepy-git-360c7725d4a82e5ad7b9ebc2e9aa459b39f5c2b4.tar.gz | |
Update the docs to the new way branch coverage works
Diffstat (limited to 'doc/branch.rst')
| -rw-r--r-- | doc/branch.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/branch.rst b/doc/branch.rst index 9cee70bf..f95f1d47 100644 --- a/doc/branch.rst +++ b/doc/branch.rst @@ -64,8 +64,8 @@ How it works When measuring branches, coverage.py collects pairs of line numbers, a source and destination for each transition from one line to another. Static analysis -of the compiled bytecode provides a list of possible transitions. Comparing -the measured to the possible indicates missing branches. +of the source provides a list of possible transitions. Comparing the measured +to the possible indicates missing branches. The idea of tracking how lines follow each other was from `Titus Brown`__. Thanks, Titus! |