Marius Gedminas wrote: > On Fri, Apr 17, 2009 at 01:30:00PM -0700, kochhar wrote: >> I'm trying to get statement-level code coverage numbers for my pylons >> app while running tests outside of nose (user, integration and load >> tests). I've tried using python-coverage and figleaf without success. >> Neither tool seems to be able to track statements within my >> application. python-coverage tells me that 0% of the lines in my app >> were executed while figleaf only provides coverage numbers for the >> standard library and Pylons library code. >> >> I ran coverage (from within my virtualenv) as: >> $ source bin/activate >> $ python bin/coverage.py -x bin/paster serve --reload development.ini > > bin/paster serve --reload spawns a subprocess. Python's coverage tools > have no way of tracing code executed in a subprocess. > > Try bin/paster serve without --reload.
Somewhat better success, the pylons framework code is tracked pretty well, but my controllers and other utilities I use are still reported at 0%. Can the coverage tools trace code executed in a separate thread (such as workers and background threads)? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
