| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
mixed up.
|
| |
|
| |
|
|
|
|
| |
the file.
|
|
|
|
| |
available everywhere.
|
|
|
|
| |
seem like Python at all. #82.
|
| |
|
|
|
|
| |
after the decimal point in coverage percentages. Finishes issue #16.
|
|
|
|
| |
result of rounding. Fixes #41 and #70.
|
|
|
|
| |
INCOMPATIBLE change.
|
|
|
|
| |
include.
|
| |
|
|
|
|
|
|
| |
the beginning of the path for any file that is going to be included in code coverage
make the --omit and --require options apply to code coverage generation as well as to reporting; This speeds up tests from 6 seconds to 1 second on my system, as well as making the resulting .coverage db include *only* the code that I care about, which helps with my code coverage progression/regression tool.
|
|
|
|
| |
helpful for directing developers to improved test coverage.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
circular.
|
| |
|
|
|
|
| |
including in rolled-up presentations.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
CodeUnit passed in.
|
| |
|
| |
|
| |
|
|
|