search

eftsung / pygr

Automatically exported from code.google.com/p/pygr
0 stars 0 forks source link

Analyze code coverage of tests, including megatests #7

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Run the tests using the figleaf code coverage analysis tool and determine
which parts of the pygr codebase are not executed by the tests.

Original issue reported on code.google.com by the.good...@gmail.com on 27 May 2008 at 4:35

GoogleCodeExporter commented 8 years ago 
Put results in the wiki, TestCodeCoverageSummary.

Original comment by the.good...@gmail.com on 27 May 2008 at 4:39

GoogleCodeExporter commented 8 years ago 
test

Original comment by the.good...@gmail.com on 27 May 2008 at 4:50

GoogleCodeExporter commented 8 years ago 
One problem with doing this is that 'protest' starts multiple processes, so 
simple
code coverage analysis won't work (figleaf and coverage.py both work by setting 
the
tracehook, which is not carried across subprocess invocations)...

Original comment by the.good...@gmail.com on 29 May 2008 at 3:38

GoogleCodeExporter commented 8 years ago 
Should be part of 0.8's "improved test coverage"

Original comment by cjlee...@gmail.com on 11 Sep 2008 at 4:12

GoogleCodeExporter commented 8 years ago 
pygrtest_common is now included & properly passes figleaf settings on to the 
child
processes.

Original comment by the.good...@gmail.com on 17 Dec 2008 at 1:54

GoogleCodeExporter commented 8 years ago

Original comment by mare...@gmail.com on 21 Feb 2009 at 1:28

GoogleCodeExporter commented 8 years ago 
Hi Titus,
please write up how to run the code coverage analysis and give that to Marek, 
so he
can verify that this issue is fixed.

Thanks!

Chris

Original comment by cjlee...@gmail.com on 4 Mar 2009 at 8:54

GoogleCodeExporter commented 8 years ago

Original comment by mare...@gmail.com on 13 Mar 2009 at 12:54

GoogleCodeExporter commented 8 years ago

Original comment by mare...@gmail.com on 13 Mar 2009 at 12:59

GoogleCodeExporter commented 8 years ago 
python runtest.py --coverage

Original comment by the.good...@gmail.com on 13 Mar 2009 at 1:31

GoogleCodeExporter commented 8 years ago 
This indeed works as it should, closing the issue. Note that this for now 
megatests 
aren't analysed, as they shall remain tied to the old test framework until all 
major 
issues with the new one have been resolved.

Original comment by mare...@gmail.com on 26 Mar 2009 at 1:54