The term quality might mean different things to different people based on their context of operation and it’s tough to have universal definition for the same.My experiments with software development started over a decade ago & exploring the ways the helps to build & deliver good quality code.The quest towards Code Quality Metrics started with the above objectives.
The discussion around Useful Code Quality Metrics at Linkedin started two months ago. I am excited over the response around the internet to this thread & there are some excellent articles around subject.
- Micheal Boltan has brought up interesting view points and also bloged about the same.
- Nigel Cheshire talks about Static Analysis metrics and expressed views on the right metrics
- Andrew Glover calls it as Code Quality’s singular metric
In the recent past Agitar comes up with CRAP4J as a code quality metric by combining Cyclomatic Complexity and Code Coverage.
In the process, we do use Static Analysis and Dynamic Analysis to derive the above mentioned metrics. Some more good articles around Code Quality are here
I wish that the info around Code Quality is helpful for my blog readers
Happy Testing…
After 642-426, you can either aim for 1Y0-327 and hence prepare for HP0-W02. You can also go directly to 646-562
Authors bio is coming up shortly.
[...] ??? ?????????? 7, 2008 ??? Ioannis Samoladas ??? ??? ?????????? blog post ??????? ?? ???????? [...]
Too bad i didnt come across this blog before. Great stuff you got here. Thanks.