Dear Open Hub Users,
We’re excited to announce that we will be moving the Open Hub Forum to
https://community.blackduck.com/s/black-duck-open-hub.
Beginning immediately, users can head over,
register,
get technical help and discuss issue pertinent to the Open Hub. Registered users can also subscribe to Open Hub announcements here.
On May 1, 2020, we will be freezing https://www.openhub.net/forums and users will not be able to create new discussions. If you have any questions and concerns, please email us at
info@openhub.net
Currently one of the main quality metrics you provide in your code analysis is the comment line percentage. Another one that would be useful would be the amount of tests in a project.
While this would probably need projects to provide some metadata about how their project is structured to do accurately, I imagine you could get a decent idea by treating files in directories named tests
or files whose names start with test_
as tests as part of the test suite. I doubt that would get many false positives, but may underestimate the size of the test suite in some projects.
Afaik, currently, ohcount detects and analyzes every file individually. This feature would probably mean having a higher level of analysis of a repository...