addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwchatcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscrosseditemptyheartfacebookfolderfullheartglobegmailgoogleimagesinstagramlinklocation-pinmagnifying-glassmailminusmoremuplabelShape 3 + Rectangle 1outlookpersonplusprice-ribbonImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruseryahoo

Re: [PhillyPUG] code coverage of a running application

From: Brian K. J.
Sent on: Monday, December 13, 2010 11:21 AM

On Mon, Dec 13, 2010 at 10:35 AM, Jason Stelzer <[address removed]> wrote:
So I've used to look at unit test coverage. Has anyone
done something where you instrument the server side, run some
functional tests, then look at a coverage report?

I use inside of Hudson. Hudson at this point detects changes in a repository, runs a bunch of tests using nose with its coverage plugin, and outputs the html reports, which are very useful for seeing visually where you're lacking.?

I just blogged about my (evolving) Hudson setup, specifically about coverage and nose, here:



Repoze looks promising. Anyone have any experiences with it?


Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
This message was sent by Jason Stelzer ([address removed]) from The Philadelphia Python Users Group (PhillyPUG).
To learn more about Jason Stelzer, visit his/her member profile:
To unsubscribe or to update your mailing list settings, click here:
Meetup, PO Box 4668 #37895 New York, New York[masked] | [address removed]

Brian K. Jones
My Blog? ? ? ? ?
Follow me? ? ?

Our Sponsors

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy