openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #04894
Re: Metrics around code
On Wed, 2011-10-19 at 04:30 -0700, Rohit Karajgi wrote:
> I agree with the HTML report, and this report can be published onto
> OpenStack Jenkins for world readability. We have some similar metrics
> for bugs.
Indeed. I haven't started looking at the bugs database yet. There are
two interesting tools though, one from Pentaho itself and one from the
same folks that develop cvsanaly. None support launchpad, so I'll need a
python-launchpadlib expert to proceed. I'll think about it when I'm done
with the code reports.
> 6. # of times a file was modified
> 7. # of lines modified per file
>
> #6 and #7 specifically can be quite useful to identify those modules that can be good targets for unit tests.
I have this data in the cvsanaly database and I think I can design a
query for it quite easily.
/stef
Follow ups
References