Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
CRAP score feature #620
The CRAP metric is a great metric to be used along with code coverage since.
Generally speaking, Crappy methods exhibit the following characteristics
Its usually challenging to write tests for complex code. Therefore code without tests are signs of crappy code ( hence lack of code coverage ). Having some code coverage indicates some degree of thought about testability and implementation.
The value of this metric is to help mitigate/reduce risk by uncovering the possible presence of crappy code. The code can
The common practices is a CRAP score of 30 or less is considered acceptable and generally anything higher should be looked at. This is really a team decision on this threshold.
Okay I can see how it can be useful - once done we'll need to work with @danielpalme to see if we can get a visualisation of this data in his awesome reporting tool.
referenced this issue
Aug 15, 2016
@akamud sorry not had a lot of time of late to work on a release - I've been waiting on another package but it seems to never want to release - I may look to make a beta release that uses the beta package I am dependant on but I am reluctant to create a release as of yet.