Quality Settings

Codacy allows you to configure some quality parameters on a project base. The menu can be accessed through the project settings, on the tab Quality Settings.

 

 

 

1. Commits


There are specific quality settings for commits that can be accessed by clicking on the corresponding Customize link:  

Screen_Shot_2018-05-04_at_18.28.58.png

As you can see, several settings are shown upon clicking:

  • Issues - The commit will be marked as having problems (a not up to standards commit) if the number of issues introduced is bigger than the selected value. Default value is 0.
  • Complexity - The commit will be marked as having problems (a not up to standards commit) if the introduced complexity is bigger than the selected value. By default this setting is off.
  • Duplication - The commit will be marked as having problems (a not up to standards commit) if the number of clones introduced is bigger than the selected value. By default this setting is off.
  • Coverage - The commit will be marked as having problems (a not up to standards commit) if the coverage introduced is smaller than the selected value. By default this setting is off.

 

2. Pull Requests


There are specific quality settings for pull requests that can be accessed by clicking on the corresponding Customize link:

Screen_Shot_2018-05-04_at_18.27.56.png

 

As you can see, several settings are shown upon clicking:

  • Issues - The pull request will be marked as having problems (a not up to standards pull request) if the number of issues introduced is bigger than the selected value. Default value is 0.
  • Complexity - The pull request will be marked as having problems (a not up to standards pull request) if the introduced complexity is bigger than the selected value. By default this setting is off.
  • Duplication - The pull request will be marked as having problems (a not up to standards pull request) if the number of clones introduced is bigger than the selected value. By default this setting is off.
  • Coverage - The pull request will be marked as having problems (a not up to standards pull request) if the coverage introduced is smaller than the selected value. This value refers to the variation of coverage on your PR, so for example if your project has 90% coverage and you want to ensure that this value doesn't decrease you should set this to 0%. By default this setting is off.

 

3. Project


There are specific quality settings for projects that can be accessed by clicking on the corresponding Customize link:

 

 

As you can see, several settings are shown upon clicking:

  • Issues are over (threshold for number of issues) - This will define the threshold shown in the dashboard.
  • File complexity is over (threshold for file complexity) - This will define the threshold shown in the complexity dashboard.
  • File is complex when over (definition of complex file) - A file will be considered complex when its complexity is over this value
  • File duplication is over (threshold for file duplication) - This will define the threshold shown in the duplication dashboard.
  • File is duplicate when over (definition of duplicated file) - A file will be considered duplicated when it has more clones than this value
  • Coverage is under (threshold for coverage) - This will define the threshold shown in the coverage dashboard.
Have more questions? Submit a request

0 Comments

Article is closed for comments.