Groovy code coverage…

After reading a post about what not to test, discussed with a friend about how to determine where you need complete code coverage, and where you don’t. Resulting idea is that the more complex the code, the more code coverage it should have. So, going to experiment with Jenkins, Sonar and GMetrics.  Article on integration is here.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s