[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:  new
     Priority:  major       |  Milestone:  1.12.0
    Component:  code        |    Version:  1.9.1
   Resolution:              |   Keywords:  usability test coverage
Launchpad Bug:              |
----------------------------+-------------------------------------
Changes (by daira):

 * owner:  davidsarah => daira
 * status:  assigned => new
 * milestone:  eventually => 1.12.0


Comment:

 Actually I'd forgotten about this ticket; #2289 is a duplicate. Its
 description was:
 > The correct command to run tests with branch coverage is:
 > {{{
 > bin/tahoe @coverage run --branch --source=src/allmydata @tahoe
 --version-and-path debug trial --rterrors allmydata.test
 > }}}
 > except that `@coverage` sometimes needs to be `@python-coverage`
 depending on how coverage is installed.
 >
 > This is impossible to remember (and the `@coverage` vs `@python-
 coverage` thing is annoying). Let's add a `--coverage` option to `python
 setup.py trial` and `python setup.py test`. Also let's have it print a
 nice error message saying how to install coverage if it's missing.

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