Comments on: Some notes on nosetests and coverage http://blog.tplus1.com/index.php/2009/05/13/some-notes-on-nosetests-and-coverage/ Programming, gardening, economics, life in Cleveland Heights Sat, 04 Feb 2012 03:03:50 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: cheap condoms http://blog.tplus1.com/index.php/2009/05/13/some-notes-on-nosetests-and-coverage/comment-page-1/#comment-3433 cheap condoms Mon, 21 Sep 2009 15:24:54 +0000 http://blog.tplus1.com/?p=340#comment-3433 I've a vim script that can load trace.py's .cover files and highlight them in the source. The .cover files have a copy of the Python source with an 8 character margin .that annotation seems like it would be<br>really useful. I've a vim script that can load trace.py's .cover files and highlight them in the source. The .cover files have a copy of the Python source with an 8 character margin .that annotation seems like it would be
really useful.

]]> By: cheap condoms http://blog.tplus1.com/index.php/2009/05/13/some-notes-on-nosetests-and-coverage/comment-page-1/#comment-2438 cheap condoms Mon, 21 Sep 2009 11:24:54 +0000 http://blog.tplus1.com/?p=340#comment-2438 I've a vim script that can load trace.py's .cover files and highlight them in the source. The .cover files have a copy of the Python source with an 8 character margin .that annotation seems like it would be<br>really useful. I've a vim script that can load trace.py's .cover files and highlight them in the source. The .cover files have a copy of the Python source with an 8 character margin .that annotation seems like it would be
really useful.

]]> By: Isis http://blog.tplus1.com/index.php/2009/05/13/some-notes-on-nosetests-and-coverage/comment-page-1/#comment-1692 Isis Thu, 04 Jun 2009 18:13:46 +0000 http://blog.tplus1.com/?p=340#comment-1692 Is that lengthy the tests report is usually!<br><br>Rina Is that lengthy the tests report is usually!

Rina

]]> By: Matt Wilson http://blog.tplus1.com/index.php/2009/05/13/some-notes-on-nosetests-and-coverage/comment-page-1/#comment-1663 Matt Wilson Thu, 14 May 2009 14:12:22 +0000 http://blog.tplus1.com/?p=340#comment-1663 I've never looked at trace; that annotation seems like it would be<br>really useful. Thanks for the tip! I've never looked at trace; that annotation seems like it would be
really useful. Thanks for the tip!

]]> By: Marius Gedminas http://blog.tplus1.com/index.php/2009/05/13/some-notes-on-nosetests-and-coverage/comment-page-1/#comment-1661 Marius Gedminas Wed, 13 May 2009 19:02:56 +0000 http://blog.tplus1.com/?p=340#comment-1661 I haven't used coverage (or figleaf) much, but I've used trace.py (which is in the Python standard library), since zope.testing.testrunner integrates with it.<br><br>I've a vim script that can load trace.py's .cover files and highlight them in the source. The .cover files have a copy of the Python source with an 8 character margin inserted in front of each line, with either the number of executions for a statement or a '>>>>>>> ' to indicate executable lines that weren't executed. I haven't used coverage (or figleaf) much, but I've used trace.py (which is in the Python standard library), since zope.testing.testrunner integrates with it.

I've a vim script that can load trace.py's .cover files and highlight them in the source. The .cover files have a copy of the Python source with an 8 character margin inserted in front of each line, with either the number of executions for a statement or a '>>>>>>> ' to indicate executable lines that weren't executed.

]]>