language agnostic - Metrics for measuring successful refactoring -
Is there a suitable metric for measuring the code refactoring?
Before and after rebooting, wanted to run searchbugs, CRAP or checkstick, it was a useful way to check whether the code has actually been improved or not changed.
I am looking for trends that can capture that can help us to improve the code review process, without wasting time without code, which would change for general personal preference is.
Before and after rewriting, searchbugs, CRAP or checkstick wanted to run Was there a useful way to check whether the code was actually improved, rather than changing?
Actually, as I have detailed in the question, the exact added value of the metrics of any metric (findbugs, CRAP, whatever) of trend .
This (development of the matrix) allows you to priority The main fixing action that you actually need to do in your code (such as trying to adopt every metric ).
Like this tool, the AIN (matrix monitoring) in this domain can be very useful.
The greeting adds to comments:
The real problem is whether the changes in the code are added, instead of just adding the changes
For this, test coverage is very important because only test (unit testing, rather large "functional testing") will give you a valid answer.
Should not be done without any obvious purpose. To do this, because it can be "more elegant" or "easy to maintain", there can be a good reason not enough to change the code in itself.
Other measures such as some bugs that will be fixed in the process, or some new functions that will be very fast as a result of the "Refacture" code. In essence, the added value of a refactoring is not fully measured by the matrix but should also be evaluated against objectives and / or milestones.
Comments
Post a Comment