[TIP] coverage.py and pyramid web framework?

Tres Seaver tseaver at palladion.com
Fri Aug 24 07:48:05 PDT 2012

Hash: SHA1

On 08/24/2012 10:35 AM, Tres Seaver wrote:
> On 08/23/2012 08:34 PM, Ben Cohen wrote:
>> The most obvious shared feature of the functions/methods that
>> report no coverage is the use of a venusian callback method
>> decorator -- this decorator marks functions/methods with declarative
>> attributes, subsequently modules are scanned for methods with those
>> attributes and then ingested by the pyramid web framework's
>> web-publishing machinery.
>> Is there some magic happening within the pyramid framework that 
>> causes coverage to fail to register when these methods are called?
>> Is anybody using coverage and pyramid together without issue …?  I
>> didn't expect so fundamental an issue with the two as the pyramid 
>> documentation has a chapter describing the use of coverage in unit 
>> tests …
> Pyramid itself runs tests with the coverage package without issues
> (run via 'setup.py nosetests --with-xunit --with-xcoverage' -- see the
> 'cover' environment in its tox.ini).  We use it routinely for apps
> built on Pyramid as well.  The venusian decorator does not do anything
> to interfere with coverage:  the attributes it adds to the decorated 
> function are used to populate Pyramid's registry during the later
> "scan" phase.

Pyramid's Jenkins:


and the instance for SubstanceD, an app written on top of Pyramide:


- -- 
Tres Seaver          +1 540-429-0999          tseaver at palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/


More information about the testing-in-python mailing list