#2289 closed enhancement (duplicate)
make tests with branch coverage easier to run
Reported by: | daira | Owned by: | daira |
---|---|---|---|
Priority: | normal | Milestone: | 1.10.1 |
Component: | packaging | Version: | 1.10.0 |
Keywords: | tests coverage usability | Cc: | |
Launchpad Bug: |
Description
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.
Change History (3)
comment:1 Changed at 2014-09-02T15:17:24Z by daira
- Keywords usability added
- Owner set to daira
- Status changed from new to assigned
comment:2 in reply to: ↑ description Changed at 2014-09-02T20:52:27Z by daira
- Resolution set to duplicate
- Status changed from assigned to closed
comment:3 Changed at 2014-11-27T03:47:24Z by daira
- Milestone changed from 1.12.0 to 1.11.0
Note: See
TracTickets for help on using
tickets.
Duplicate of #1698.