diff options
| author | Ned Batchelder <ned@nedbatchelder.com> | 2019-06-11 08:29:28 -0400 |
|---|---|---|
| committer | Ned Batchelder <ned@nedbatchelder.com> | 2019-06-11 08:29:28 -0400 |
| commit | 4f6365167a0921335e1e365a3cff05a5907943dd (patch) | |
| tree | 315e13c2bd62288e009da2d17eaf6a42380c7fbd /doc/contexts.rst | |
| parent | cc008dd00a2197792ae55d68b46e760c630b1189 (diff) | |
| download | python-coveragepy-git-4f6365167a0921335e1e365a3cff05a5907943dd.tar.gz | |
Docs for --contexts and --show-contexts
Diffstat (limited to 'doc/contexts.rst')
| -rw-r--r-- | doc/contexts.rst | 29 |
1 files changed, 21 insertions, 8 deletions
diff --git a/doc/contexts.rst b/doc/contexts.rst index f1796aae..e8aa4ed4 100644 --- a/doc/contexts.rst +++ b/doc/contexts.rst @@ -44,10 +44,10 @@ the configuration file. Dynamic contexts ---------------- -Dynamic contexts are found during execution. They started from the question, -"what test ran this line?," but have been generalized to allow any kind of -context tracking. As execution proceeds, the dynamic context changes -to record the context of execution. Separate data is recorded for each +Dynamic contexts are found during execution. They are most commonly used to +answer the question "what test ran this line?," but have been generalized to +allow any kind of context tracking. As execution proceeds, the dynamic context +changes to record the context of execution. Separate data is recorded for each context, so that it can be analyzed later. There are three ways to enable dynamic contexts: @@ -68,7 +68,7 @@ The ``[run] dynamic_context`` setting has only one option now. Set it to Each test function you run will be considered a separate dynamic context, and coverage data will be segregated for each. A test function is any function -whose names starts with "test". +whose name starts with "test". If you have both a static context and a dynamic context, they are joined with a pipe symbol to be recorded as a single string. @@ -80,10 +80,23 @@ then the code run by the test runner before (and between) tests will be in the empty context. +.. _context_reporting: + Context reporting ----------------- -There is currently no support for using contexts during reporting. I'm -interested to `hear your ideas`__ for what would be useful. +The ``coverage report`` and ``coverage html`` commands both accept +``--contexts`` option, a comma-separated list of shell-style wildcards. The +report will be limited to the contexts that match one of those contexts. + +The ``coverage html`` command also has ``--show-contexts``. If set, the HTML +report will include an annotation on each covered line indicating the number of +contexts that executed the line. Hovering over the annotation displays a list +of the contexts. + + +Raw data +-------- -__ https://nedbatchelder.com/site/aboutned.html +For more advanced reporting or analysis, the .coverage data file is a SQLite +database. TODO: explain the schema. |
