-
Book Overview & Buying
-
Table Of Contents
-
Feedback & Rating

Sonar Code Quality Testing Essentials
By :

Writing code is not a monolithic procedure and is never written once. At least a couple of revisions take place before we consider it to be final. Of course, when a bug arises we are forced to revise and correct or improve the code but it is best to code and develop pro-actively. Adding code reviews as an additional process before committing code helps identify problematic areas early and ensure better quality. As a matter of fact, we could say that the Sonar platform reviews code from many perspectives, generating results over different axes. But systematic examination and code inspection by team developers is irreplaceable.
To quote Eric S. Raymond's Linus's Law named in honor of Linus Torvalds:
Linus's Law:
Given enough eyeballs, all bugs are shallow.
The most common ways to perform code reviews are:
Via e-mail communication: Report on code expecting to hear back
Pair programming: The developers work closely together
Software Managed Reviews: Use tools to streamline the process...
Change the font size
Change margin width
Change background colour