[TIP] coverage.py against a server

[Lucian Ciufudean]

Sorry for all these iterations, here is a more consistent (but long) email.

After not being able to run 'coverage run pyc_file.pyc', I created a dummy
driver main.py file that uses the compiled modules.

root at spahire pyc]# ls -la
total 20
drwxr-xr-x. 2 root root 4096 Sep 18 13:20 .
drwxr-xr-x. 4 root root 4096 Sep 17 15:58 ..
-rw-r--r--. 1 root root   28 Sep 18 13:01 main.py
-rw-------. 1 root root  187 Sep 17 15:59 test_coverage_callee.pyc
-rw-------. 1 root root  212 Sep 17 15:59 test_coverage_caller.pyc
[root at spahire pyc]# cat  main.py
import test_coverage_caller

The source files for the 2 pyc files are here:

[root at spahire pyc]# ls ../src
test_coverage_callee.py  test_coverage_caller.py

Further, I run coverage, I get a warning but a data file .coverage is
created:

[root at spahire pyc]# coverage run --source=../src main.py
1
2
2.1
2.2
2.3
Coverage.py warning: No data was collected.
[root at spahire pyc]# ls -l .coverage
-rw-r--r--. 1 root root 180 Sep 18 13:23 .coverage

--include does not make a difference:

[root at spahire pyc]# coverage run --source=../src --include='*' main.py
1
2
2.1
2.2
2.3
Coverage.py warning: No data was collected.
[root at spahire pyc]# ls -l .coverage
-rw-r--r--. 1 root root 180 Sep 18 13:38 .coverage

As expected, report shows nothing is covered:

[root at spahire pyc]# coverage report --include='*test*'
Name                                                     Stmts   Miss  Cover
----------------------------------------------------------------------------
/root/lucian/coverage/module1/src/test_coverage_callee       3      3     0%
/root/lucian/coverage/module1/src/test_coverage_caller       3      3     0%
----------------------------------------------------------------------------
TOTAL                                                        6      6     0%

report does not accept --source, might this be the root to all evil?

[root at spahire pyc]# coverage report --include='*test*' --source=../src
no such option: --source
Use 'coverage help' for help.

No warning when using run without options, but the report is again wrong:

[root at spahire pyc]# coverage run main.py
1
2
2.1
2.2
2.3
[root at spahire pyc]# coverage report
Name                   Stmts   Miss  Cover
------------------------------------------
main                       1      0   100%
test_coverage_callee   NoSource: No source for code:
'/root/lucian/coverage/module1/pyc/test_coverage_callee.py'
test_coverage_caller   NoSource: No source for code:
'/root/lucian/coverage/module1/pyc/test_coverage_caller.py'

Same thing with a configuration file:
[root at spahire pyc]# cat .coveragerc
[run]
source=../src/
include=*

So now I turn to the api + the same .coveragerc, the same thing:

[root at spahire pyc]# cat api.py
import coverage
cov = coverage.coverage()
cov.start()
import test_coverage_caller
cov.stop()
cov.save()

[root at spahire pyc]# python api.py
1
2
2.1
2.2
2.3
Coverage.py warning: No data was collected.

As for your suggestion with [paths], the docs suggest to me that this is
for combining data.

Lucian



On Wed, Sep 18, 2013 at 1:20 PM, Ned Batchelder <ned at nedbatchelder.com>wrote:

>  On 9/18/13 3:42 AM, Lucian Ciufudean wrote:
>
> Here is how I ran coverage:
>
>      coverage run --source=../src main.py
>
>  main.py imports a pyc file that resides in the same folder. The source
> of this pyc file is available in ../src.
> (I created main.py just to go around the bug that you submitted above)
>
>   You don't mention the exact errors you saw (details matter), but in
> your previous message you mentioned the problem being while reporting.
> You'll also have to specify the source directory during the "coverage html"
> command (or coverage.html() call).  A good way to do this is with a
> .coveragerc file.
>
> --Ned.
>
>
>  Lucian
>
>
> On Wed, Sep 18, 2013 at 5:05 AM, Ned Batchelder <ned at nedbatchelder.com>wrote:
>
>>  On 9/17/13 7:42 AM, Lucian Ciufudean wrote:
>>
>> Hi guys,
>>
>>  I embarked on the road of obtaining a coverage report for functional
>> tests against a server process. The server is deployed as .pyc files, and
>> the source files can be made available in a separate subversion working
>> folder. I wouldn't want to edit any existing .py files.
>>
>>  Can coverage work with .pyc files - I am getting errors when using
>> coverage run main.pyc from the command line, so maybe with the API?
>>
>>
>>  Hmm, you're right: "coverage run foo.pyc" does not work. I've created a
>> ticket for this:
>> https://bitbucket.org/ned/coveragepy/issue/264/coverage-wont-run-pyc-files
>>
>>
>>  I tired this also, my custom code is run but it can not find the source
>> files at the time of coverage.html_report() although I passed the directory
>> of source files to coverage.coverage.
>>
>>
>>  You'll have to show details of how you tried to run coverage.  If the
>> .py files are in the places reported by your program, then it should work.
>> You can also use the [paths] section of a .coveragerc to instruct coverage
>> where the files are.
>>
>> --Ned.
>>
>>
>>  Thanks a lot,
>> Lucian
>>
>>
>> _______________________________________________
>> testing-in-python mailing listtesting-in-python at lists.idyll.orghttp://lists.idyll.org/listinfo/testing-in-python
>>
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idyll.org/pipermail/testing-in-python/attachments/20130918/2fa61d75/attachment-0001.htm>