<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Ross, <br>
<br>
Thanks so much for taking this on.<br>
<br>
On the omit handling: it's very clear that I need to beef up how to
control coverage.py's attention. The current handling is simplistic.
In fact, the current scheme doesn't make much sense: data is collected
for all code, then at the end, a bunch of files are omitted from the
report. Better would be to ignore the files during data collection.<br>
<br>
In addition, I'd like to add a .ini file for coverage.py to control all
sorts of aspects of its execution, including which files to ignore.<br>
<br>
So I want to make sure that these plug-ins play well with those
(future) improvements to coverage. I know this is a bit much to ask at
this point.<br>
<br>
Lastly, I'm trying to get my head around how to unit test this plug-in
code!<br>
<br>
--Ned.<br>
<br>
Ross Lawley wrote:
<blockquote
cite="mid:305366200911200430h35a6567fyd84b81c9994766f3@mail.gmail.com"
type="cite">Hi,
<div><br>
</div>
<div>Thanks for the heads up about the repository. I wasn't too sure
what the situation was with bitbucket as I'm new to hg, but seems very
similar to github work flows so all good there! I found a good hg
manual: <a moz-do-not-send="true" href="http://hgbook.red-bean.com/">http://hgbook.red-bean.com/</a>
<div><br>
</div>
<div>Anyway, I've branched off coveragepy and created a repo:</div>
<div><br>
</div>
<div><a moz-do-not-send="true"
href="http://bitbucket.org/rozza/coverage-test-runner/">http://bitbucket.org/rozza/coverage-test-runner/</a></div>
<div><br>
</div>
<div>I've added runner.py which is a utility wrapper for test
plugins. I've written a pytest and a nose plugin, I've use the pytest
one locally with my codebase and it works great. I've tested the nose
plugin but haven't actually used it in anger - so it may need tweaking!</div>
<div><br>
</div>
<div>Any feedback let me know - I'm not sure on the option parsing -
you'll see why!</div>
<div><br>
</div>
<div>Another area of note is I've tweaked the file / code omit code:</div>
<div><br>
</div>
<div>1) So that I can use a file with each rule on a line or command
line comma separated as normal</div>
<div>2) I've moved the code_unit_factory file omit logic round so I
could monkey patch it which is in the plugins - so remove that if you
don't need it! I know its not ideal it scratched my itch at the moment.</div>
<div><br>
</div>
<div>Basically it means I can have a file in my repo that is used to
filter all files on all work environments (mac osx / unix) eg:</div>
<div><br>
</div>
<div>
<div>conftest</div>
<div>/tests/</div>
<div>/usr/lib/python.*/.*.py</div>
<div>/usr/local/lib/python.*/.*.py</div>
<div>/usr/share/*</div>
<div>/var/lib/python-support/.*</div>
<div>/System/Library/*</div>
<div>/Library/*</div>
<div>/opt/subversion/*</div>
<div>.*.html</div>
<div>/tests/</div>
<div><br>
</div>
<div>Which seems more suited to running a test suite.</div>
<div><br>
</div>
<div>Ross</div>
</div>
</div>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
testing-in-python mailing list
<a class="moz-txt-link-abbreviated" href="mailto:testing-in-python@lists.idyll.org">testing-in-python@lists.idyll.org</a>
<a class="moz-txt-link-freetext" href="http://lists.idyll.org/listinfo/testing-in-python">http://lists.idyll.org/listinfo/testing-in-python</a>
</pre>
</blockquote>
</body>
</html>