Chris McDonough wrote:

> Here's the set of commands that get run to test e.g. repoze.bfg:
> /opt/Python-2.6.4/bin/virtualenv --no-site-packages r$SVN_REVISION/
> r$SVN_REVISION/bin/easy_install nose coverage nosexcover

No sex cover, ey? That sounds like an STD risk.

> cd repoze.bfg-trunk
> ../r$SVN_REVISION/bin/python develop
> ../r$SVN_REVISION/bin/python nosetests --with-xunit \
>       --with-xcoverage

Cool. I guess there's a standard there somewhere that both Cobertura and 
nose adheres to. I wonder how hard it is to run Zope/Plone tests through 
nose in this way. I'm guessing quite.

>>     - How did you get Cobertura integration going? I've been using
>> z3c.coverage + the NCover plugin, but yours looks nicer.
> Vis nosexcover and using nose to run the tests (that's the --with-xunit and
> --with-xcoverage hair), then choosing "Publish Cobertura Coverage Report" in
> the configuration.

Yeah, makes sense.


Author of `Professional Plone Development`, a book for developers who
want to work with Plone. See

Repoze-dev mailing list

Reply via email to