microsoft / azure-devops-intellij
Source Code Overview

Analysis scope, overview of main, test, generated, deployment, build, and other code.

Source Code Analysis Scope
Files includes and excluded from analyses
txt
properties
gitattributes
  • 15 extensions are included in analyses: java, kt, gradle, xml, txt, bat, properties, gitignore, svg, gitattributes, ps1, sh, md, json, yml
  • 7 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (7 files).
    • exclude files with path like ".*/gradle/wrapper/.*" (Gradle) (1 file).
    • exclude files with path like ".*/extern(al)?/.*" (Dependencies) (110 files).
    • exclude files with path like ".*/git[-]history[.]txt" (Git history) (1 file).
    • exclude files with path like ".*/git[-][a-zA-Z0-9_]+[.]txt" (Git data exports for sokrates analyses) (0 files).
    • exclude files with path like ".*/sokrates_conventions[.]json" (Sokrates scoping conventions) (1 file).
    • exclude files with path like ".*[.]txt" (Text files) (1 file).
Overview of Analyzed Files
Basic stats on analyzed files
Intro
For analysis purposes we separate files in scope into several categories: main, test, generated, deployment and build, and other.

  • The main category contains all manually created source code files that are being used in the production.
  • Files in the main category are used as input for other analyses: logical decomposition, concerns, duplication, file size, unit size, and conditional complexity.
  • Test source code files are used only for testing of the product. These files are normally not deployed to production.
  • Build and deployment source code files are used to configure or support build and deployment process.
  • Generated source code files are automatically generated files that have not been manually changed after generation.
  • While a source code folder may contain a number of files, we are primarily interested in the source code files that are being written and maintained by developers.
  • Files containing binaries, documentation, or third-party libraries, for instance, are excluded from analysis. The exception are third-party libraries that have been changed by developers.

main32570 LOC (67%) 358 files
test13889 LOC (28%) 152 files
generated0 LOC (0%) 0 files
build and deployment574 LOC (1%) 11 files
other895 LOC (1%) 8 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 358 files match defined criteria (32,570 lines of code, 100.0% vs. main code):
    • 345 *.java files (31,496 lines of code)
    • 12 *.kt files (1,011 lines of code)
    • 1 *.yml files (63 lines of code)
  • " *.java" is biggest, containing 96.7% of code.
  • " *.yml" is smallest, containing 0.19% of code.


*.java31496 LOC (96%) 345 files
*.kt1011 LOC (3%) 12 files
*.yml63 LOC (<1%) 1 files
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*/[Tt]est/.*".
    • files with paths like ".*/[Tt]ests/.*".
    • files with any line of content like ".*/simpletest/.*".
  • 152 files match defined criteria (13,889 lines of code, 42.6% vs. main code):
    • 145 *.java files (13,647 lines of code)
    • 7 *.kt files (242 lines of code)
  • " *.java" is biggest, containing 98.26% of code.
  • " *.kt" is smallest, containing 1.74% of code.


*.java13647 LOC (98%) 145 files
*.kt242 LOC (1%) 7 files
Build and Deployment Code
Source code used to configure or support build and deployment process.
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitattributes".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*[.]bat".
    • files with paths like ".*[.]sh".
    • files with paths like ".*[.]gradle".
  • 11 files match defined criteria (574 lines of code, 1.8% vs. main code):
    • 7 *.gradle files (358 lines of code)
    • 3 *.bat files (176 lines of code)
    • 1 *.sh files (40 lines of code)
  • " *.gradle" is biggest, containing 62.37% of code.
  • " *.sh" is smallest, containing 6.97% of code.


*.gradle358 LOC (62%) 7 files
*.bat176 LOC (30%) 3 files
*.sh40 LOC (6%) 1 files
Other Code
properties
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]json".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*[.]txt".
    • files with paths like ".*/LICENSE[.][a-z0-9]+".
    • files with paths like ".*[.]md".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*/config/checkstyle/.*".
    • files with paths like ".*[.]properties".
    • files with paths like ".*[.]svg".
    • files with paths like ".*[.](xml|xsd|robot|sql|pgsql|dashboard|profile|ipynb|raml|avsc|al)".
  • 8 files match defined criteria (895 lines of code, 2.7% vs. main code):
    • 2 *.properties files (573 lines of code)
    • 4 *.xml files (230 lines of code)
    • 1 *.md files (86 lines of code)
    • 1 *.svg files (6 lines of code)
  • " *.properties" is biggest, containing 64.02% of code.
  • " *.svg" is smallest, containing 0.67% of code.


*.properties573 LOC (64%) 2 files
*.xml230 LOC (25%) 4 files
*.md86 LOC (9%) 1 files
*.svg6 LOC (<1%) 1 files
Analyzers
Info about analyzers used for source code examinations.
  • *.java files are analyzed with JavaAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Advanced code cleaning (empty lines and comments removed for LOC calculations, additional cleaning for duplication calculations)
    • Unit size analysis
    • Conditional complexity analysis
    • Advanced heuristic dependency analysis (based on package names)
  • *.kt files are analyzed with KotlinAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Advanced code cleaning (empty lines and comments removed for LOC calculations, additional cleaning for duplication calculations)
    • Unit size analysis
    • Conditional complexity analysis
    • Basic heuristic dependency analysis (based on imports and package statements)
  • *.yml files are analyzed with YamlAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Advanced code cleaning (empty lines and comments removed for LOC calculations, additional cleaning for duplication calculations)
    • No unit size analysis
    • No conditional complexity analysis
    • No dependency analysis


2022-01-30 10:25