microsoft / team-explorer-everywhere
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
properties
prefs
project
txt
classpath
ini
cmd
sl
proj
patch
gitattributes
xsd
launch
  • 25 extensions are included in analyses: java, properties, prefs, xml, project, html, txt, classpath, htm, c, h, ini, cmd, sl, proj, patch, md, gitignore, css, js, gitattributes, sh, xsd, json, launch
  • 6 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (140 files).
    • exclude files with path like ".*/cache/.*" (Caches) (32 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) (28 files).
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.

main575788 LOC (87%) 5987 files
test14139 LOC (2%) 161 files
generated0 LOC (0%) 0 files
build and deployment619 LOC (<1%) 2 files
other64098 LOC (9%) 530 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
cmd
proj
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 5987 files match defined criteria (575,788 lines of code, 100.0% vs. main code):
    • 5,906 *.java files (564,479 lines of code)
    • 21 *.c files (5,680 lines of code)
    • 27 *.html files (2,825 lines of code)
    • 10 *.h files (763 lines of code)
    • 2 *.css files (617 lines of code)
    • 7 *.cmd files (573 lines of code)
    • 7 *.htm files (528 lines of code)
    • 5 *.proj files (171 lines of code)
    • 2 *.js files (152 lines of code)
  • " *.java" is biggest, containing 98.04% of code.
  • " *.js" is smallest, containing 0.03% of code.


*.java564479 LOC (98%) 5906 files
*.c5680 LOC (<1%) 21 files
*.html2825 LOC (<1%) 27 files
*.h763 LOC (<1%) 10 files
*.css617 LOC (<1%) 2 files
*.cmd573 LOC (<1%) 7 files
*.htm528 LOC (<1%) 7 files
*.proj171 LOC (<1%) 5 files
*.js152 LOC (<1%) 2 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]ests/.*".
    • files with paths like ".*/[Tt]est/.*".
    • files with paths like ".*/[Ss]pecs/.*".
    • files with any line of content like ".*/simpletest/.*".
  • 161 files match defined criteria (14,139 lines of code, 2.5% vs. main code):
    • 159 *.java files (14,001 lines of code)
    • 2 *.html files (138 lines of code)
  • " *.java" is biggest, containing 99.02% of code.
  • " *.html" is smallest, containing 0.98% of code.


*.java14001 LOC (99%) 159 files
*.html138 LOC (<1%) 2 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 ".*/[.]gitignore".
    • files with paths like ".*/build[.]xml".
    • files with paths like ".*/[.]gitattributes".
    • files with paths like ".*[.]sh".
  • 2 files match defined criteria (619 lines of code, 0.1% vs. main code). All matches are in *.sh files.


*.sh619 LOC (100%) 2 files
Other Code
properties
patch
xsd
ini
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 ".*[.]md".
    • files with paths like ".*[.]txt".
    • files with paths like ".*/LICENSE[.][a-z0-9]+".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*[.]properties".
    • files with paths like ".*[.]patch".
    • files with paths like ".*[.]ini".
    • files with paths like ".*/[Ss]amples/.*".
    • files with paths like ".*[.](xml|xsd|robot|sql|pgsql|dashboard|profile|ipynb|raml|avsc|al)".
  • 530 files match defined criteria (64,098 lines of code, 11.1% vs. main code):
    • 389 *.properties files (42,575 lines of code)
    • 77 *.xml files (18,169 lines of code)
    • 50 *.java files (2,817 lines of code)
    • 3 *.md files (245 lines of code)
    • 3 *.patch files (232 lines of code)
    • 1 *.xsd files (32 lines of code)
    • 7 *.ini files (28 lines of code)
  • " *.properties" is biggest, containing 66.42% of code.
  • " *.ini" is smallest, containing 0.04% of code.


*.properties42575 LOC (66%) 389 files
*.xml18169 LOC (28%) 77 files
*.java2817 LOC (4%) 50 files
*.md245 LOC (<1%) 3 files
*.patch232 LOC (<1%) 3 files
*.xsd32 LOC (<1%) 1 files
*.ini28 LOC (<1%) 7 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)
  • *.c files are analyzed with CStyleAnalyzer:
    • 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
    • No dependency analysis
  • *.html files are analyzed with HtmlAnalyzer:
    • 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
  • *.h files are analyzed with CppAnalyzer:
    • 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
  • *.css files are analyzed with CssAnalyzer:
    • 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
  • *.cmd files are analyzed with DefaultLanguageAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Basic code cleaning (empty lines removed for LOC calculations and duplication calculations)
    • No unit size analysis
    • No conditional complexity analysis
    • No dependency analysis
  • *.htm files are analyzed with HtmlAnalyzer:
    • 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
  • *.proj files are analyzed with XmlAnalyzer:
    • 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
  • *.js files are analyzed with JavaScriptAnalyzer:
    • 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
    • No dependency analysis

2022-01-30 13:28