[TIP] coverage.py input file

Ned Batchelder ned at nedbatchelder.com
Thu Aug 4 06:59:19 PDT 2011

Programmatically, there's 
coverage.coverage(data_file="/path/to/datafile"), and in the 
configuration file, there's "[run] data_file=/path/to/datafile".  Is 
there another way you need to specify it?


On 8/2/2011 10:18 AM, Alfredo Deza wrote:
> I was trying to look for an option in `coverage.py` that would accept 
> a `.coverage` file as an input.
> Usually `.coverage` is placed from wherever the command was run.
> Is there such an option and I am just failing to find it? Or is this 
> something that could be accepted as
> a feature request?
> Probably something that makes coverage.py crawl back up in directories 
> until it finds a `.coverage` file
> (a la git/hg) would make even more sense than an input file flag.
> My reasoning for this is because a lot of times I find myself several 
> directories deep into a project that has
> run coverage before but I can't get the proper report since there is 
> no `.coverage` in the current directory.
> Has anyone experienced something like this before? What are your 
> workarounds (if any) ?
> Thanks!
> -Alfredo
> _______________________________________________
> testing-in-python mailing list
> testing-in-python at lists.idyll.org
> http://lists.idyll.org/listinfo/testing-in-python
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idyll.org/pipermail/testing-in-python/attachments/20110804/a49606e1/attachment.html>

More information about the testing-in-python mailing list