Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 18 Current »

Like Bugs and Potential Bugs, Coding Standards Breaches are tracked through the issues mechanism. While it's difficult to match each of the seven deadly coding sins to an analogous deadly spiritual sin, you might match this one to pride - pride that your code is so good you don't need to be bothered with which line you and your teammates all agreed to put the curly brace on. Or you might tag it to sloth - because you're too lazy to learn and follow your team's standards about whether or not to use spaces in if statements.

Either way this sin is about not following the team-agreed standards. And that lack of compliance means that other people on the team will be tripped up when they try to read this non-compliant code, and spend extra time just trying to parse out what's happening - time that could have been used for moving the code base forward.

To monitor the compliance with coding standards, add the Issues and Technical Debt widget to your dashboard:

It is possible to check compliance with coding standards on both source code and unit tests code.

Use the differential views to monitor new issues.

You can set your coding standards (active coding rules, severity, etc.) through the Quality Profiles administration page.

 

  • No labels