[tahoe-lafs-trac-stream] [Tahoe-LAFS] #1698: the preferred cmdline to run tests under coverage is pretty huge, and comes in two flavors due to Debian renaming of the script

[Tahoe-LAFS]

#1698: the preferred cmdline to run tests under coverage is pretty huge, and comes
in two flavors due to Debian renaming of the script
----------------------------+-------------------------------------
     Reporter:  davidsarah  |      Owner:  daira
         Type:  defect      |     Status:  assigned
     Priority:  normal      |  Milestone:  1.12.0
    Component:  code        |    Version:  1.9.1
   Resolution:              |   Keywords:  usability test coverage
Launchpad Bug:              |
----------------------------+-------------------------------------

Comment (by warner):

 Huh. `coverage run bin/tahoe debug trial` has the not-really-covered
 problem. `bin/tahoe @coverage run @tahoe debug trial` seems to get the
 right data. I didn't think those two would behave differently.

 incidentally, my plan is to change the Makefile to let "make test-
 coverage" work (and let you set COVERAGE=python-coverage" if you're
 running on ubuntu), and make travis get coverage, but put off changing the
 buildbot to get coverage for a while. I think we can let travis+coveralls
 take responsibility for rendering and archiving coverage data for public
 consumption, and remove that stuff from the buildbot (which is currently
 disabled now anyways)

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1698#comment:12>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage