| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
properly for reporting functions. This is now fixed.
|
| |
|
|
|
|
| |
available everywhere.
|
|
|
|
| |
seem like Python at all. #82.
|
| |
|
| |
|
|
|
|
| |
'measured'.
|
| |
|
| |
|
|
|
|
| |
for --include.
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
#37.
|
| |
|
| |
|
|
|
|
| |
the paths displayed in the HTML are kind of heinous.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|