[TIP] nose/py.test plugins

[Ned Batchelder]

holger krekel wrote:
> Hi Ned, Ross, David, 
> I think a coverage configuration file makes a lot of sense.  
>
>   
>> 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.
>>     
>
> 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 https://bitbucket.org/hpk42/py-trunk" for the setup/distribute_setup 
> i came up with.
>
>   
>> Lastly, I'm trying to get my head around how to unit test this plug-in code!
>>     
>
> 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
>
>   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idyll.org/pipermail/testing-in-python/attachments/20091125/d9d7b9fa/attachment.html>