<!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">
<br>
<br>
holger krekel wrote:
<blockquote cite="mid:20091125091522.GA29390@trillke.net" type="cite">
<pre wrap="">Hi Ned, Ross, David,
I think a coverage configuration file makes a lot of sense.
</pre>
<blockquote type="cite">
<pre wrap="">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.
</pre>
</blockquote>
<pre wrap=""><!---->
A config file would help to eliminate tons of command line options from the
plugins and ease coverage moving on consistently.
Btw, I think that we could put all plugin code (for nose and py.test) into a single
file and setuptools-register both nose and py.test plugin entry points.
Btw2, Distribute offers the setuptools-API on Python2 and Python3. Feel free to
"hg clone <a class="moz-txt-link-freetext" href="https://bitbucket.org/hpk42/py-trunk">https://bitbucket.org/hpk42/py-trunk</a>" for the setup/distribute_setup
i came up with.
</pre>
<blockquote type="cite">
<pre wrap="">Lastly, I'm trying to get my head around how to unit test this plug-in code!
</pre>
</blockquote>
<pre wrap=""><!---->
The test plugins do not have much internal logic other than glueing
test plugin machinery and coverage functionality. So i think that
some automated functional tests go a long way.
Question: do you want to generally package the nose/py.test plugin
code with the coverage package?
Currently nose comes with a builtin coverage plugin (where David
just recently posted an update) and i guess this would need
to change?!
cheers,
holger
</pre>
</blockquote>
</body>
</html>