[TIP] Running Coverage.py with Production load and getting the report every hour

Ned Batchelder ned at nedbatchelder.com
Sun Jan 22 15:55:16 PST 2017

On 1/22/17 4:04 AM, Ankit Chopra wrote:
> Hi All, 
> We want to run coverage.py in our production application. We want to
> discover the obsolete code and see the report with actual production
> load. 
> I have played with coverage.py tool and have seen that it creates the
> report after execution/termination and till that time it keeps
> everything in memory.  
> Is there a way I can configure it to dump the report at regular
> interval like every hour or daily without stopping my application. and
> Later on I can merge and create a consolidated report. 
What kind of application is it, why does it run so long, and is there a
natural unit of work that you could take advantage of? For example, if
it's a web application, the simplest thing would be to measure coverage
on a worker process, and start and stop workers on the frequency you want.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idyll.org/pipermail/testing-in-python/attachments/20170122/9cb25386/attachment.htm>

More information about the testing-in-python mailing list