I wonder if anything can or should be done to make tox and coverage work
better together. In particular, I have to add some icky and fragile code to
my coverage.ini to get reasonable results from a `tox -e coverage` run.
-----snip snip-----
[run]
branch = true
parallel = true
omit =
setup*
*/showme.py
.tox/coverage/lib/python2.7/site-packages/*
[paths]
source =
mailman
.tox/coverage/lib/python*/site-packages/mailman
-----snip snip-----
I don't like having to equivalence the in-tree directory ('mailman') with the
tox venv site-packages directory, but this is necessary because some tests run
from executables created in the venv. I'd like for coverage to do the [paths]
bits automatically when it detects its running under tox.
I also don't like having to explicitly omit everything else in the tox venv's
site-packages. It seems like since coverage already omits stuff in the
system's site-packages, it could do the same with the tox venv site-packages.
Cheers,
-Barry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.idyll.org/pipermail/testing-in-python/attachments/20141112/517c2d6b/attachment.pgp>