From d6a7a11f8c5a8e73a9dfd9a1ce602df775d04586 Mon Sep 17 00:00:00 2001 From: Ned Batchelder Date: Thu, 23 Jul 2015 21:22:30 -0400 Subject: Refer to the project consistenly as coverage.py. #275 --- TODO.txt | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) (limited to 'TODO.txt') diff --git a/TODO.txt b/TODO.txt index 0062dbe..bf20d99 100644 --- a/TODO.txt +++ b/TODO.txt @@ -1,4 +1,4 @@ -Coverage TODO +Coverage.py TODO Key: * Heading @@ -126,7 +126,7 @@ x Tricky swapping of collector like figleaf, pycov, et al. (Don't need to do 3: c = 3 if the coverage data shows 1,2,3, it was if-then. if it's 1,3, then the missing else was executed. -- API for getting coverage data. ++ API for getting coverage data. - Instruction tracing instead of line tracing. - Path tracing (how does this even work?) - Count execution of lines @@ -143,7 +143,7 @@ x Tricky swapping of collector like figleaf, pycov, et al. (Don't need to do directory. - Why can't a morf also be a string, the name of a module? - ignore by module as well as file? -+ Use a .coveragerc file to control Coverage without the programmatic API. ++ Use a .coveragerc file to control coverage.py without the programmatic API. - Add a --data switch to explicitly control the data file on the command line. x Why can't you specify execute (-x) and report (-r) in the same invocation? Maybe just because -x needs the rest of the command line? @@ -156,7 +156,7 @@ x Why can't you specify execute (-x) and report (-r) in the same invocation? class definitions, etc, when coverage is started after the class is defined. - Different categories of exclude pragma? So you can enable and disable them from the command line, to reconsider exclusions. -+ Reporting on files never touched by coverage (package completeness) ++ Reporting on files never touched by coverage.py (package completeness) - A setup.py command? http://jeetworks.org/node/50 - Deltas: indicate the change in coverage percentage from the last run. + Show lines missing rather than lines run in the reporting, since that's what @@ -177,7 +177,7 @@ x Why can't you specify execute (-x) and report (-r) in the same invocation? + Clickable column headers on the index page. + Syntax coloring in HTML report. + Dynamic effects in HTML report. - + Footer in reports pointing to coverage home page. + + Footer in reports pointing to coverage.py home page. + Baseline grid for linenumber font. + Separate out css and HTML. + Does it work right with utf-8 source files? http://www.python.org/dev/peps/pep-0263/ @@ -196,10 +196,10 @@ x Why can't you specify execute (-x) and report (-r) in the same invocation? - ignore (files not to collect) - exclude (lines not to report as missed) - omit (files not to report) - - Changes from coverage 2.x: + - Changes from coverage.py 2.x: - Bare "except:" lines now count as executable code. - Double function decorators: all decorator lines count as executable code. - - Document the .coverage file format. + x Document the .coverage file format. + HTML reporting. - Much more detail about what's in the report. - References between pages are off: @@ -220,8 +220,8 @@ x Why can't you specify execute (-x) and report (-r) in the same invocation? * Installation -x How will Coverage package install over coverage.py module? -x pip can't install it: it reads the coverage html page, and finds the kit link, +x How will coverage.py package install over coverage.py module? +x pip can't install it: it reads the coverage.py html page, and finds the kit link, but then can't handle the root-relative link. @@ -263,13 +263,13 @@ x pip can't install it: it reads the coverage html page, and finds the kit link, + Switch to a real test runner, like nose. + Test both the C trace function and the Python trace function. + parser.py has no direct tests. -- Tests about the .coverage file. ++ Tests about the .coverage file. + Tests about the --long-form of arguments. + Tests about overriding the .coverage filename. - Tests about parallel mode. + Tests about assigning a multi-line string. - Tests about tricky docstrings. -+ Coverage test Coverage! ++ Coverage test coverage.py! - Tests that tracing stops after calling stop() - More intensive thread testing. x Tests about the "import __main__" in cmdline.py -- cgit v1.2.1