microsoft / vs-boost-unit-test-adapter
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
resx
csproj
gv
txt
xsd
vsixmanifest
gitattributes
vstemplate
g4
props
  • 19 extensions are included in analyses: cs, xml, resx, csproj, gv, txt, md, xsd, vsixmanifest, gitattributes, ps1, bat, json, yml, cpp, vstemplate, gitignore, g4, props
  • 6 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (2 files).
    • exclude files with path like ".*[.]resx" (The resx resource files) (15 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) (5 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.

main9999 LOC (73%) 139 files
test617 LOC (4%) 9 files
generated1696 LOC (12%) 8 files
build and deployment1041 LOC (7%) 10 files
other320 LOC (2%) 37 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
gv
g4
vsixmanifest
vstemplate
props
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 139 files match defined criteria (9,999 lines of code, 100.0% vs. main code):
    • 127 *.cs files (9,596 lines of code)
    • 5 *.gv files (145 lines of code)
    • 1 *.g4 files (130 lines of code)
    • 1 *.yml files (41 lines of code)
    • 1 *.vsixmanifest files (39 lines of code)
    • 1 *.vstemplate files (16 lines of code)
    • 1 *.ps1 files (13 lines of code)
    • 1 *.props files (12 lines of code)
    • 1 *.cpp files (7 lines of code)
  • " *.cs" is biggest, containing 95.97% of code.
  • " *.cpp" is smallest, containing 0.07% of code.


*.cs9596 LOC (95%) 127 files
*.gv145 LOC (1%) 5 files
*.g4130 LOC (1%) 1 files
*.yml41 LOC (<1%) 1 files
*.vsixmanifest39 LOC (<1%) 1 files
*.vstemplate16 LOC (<1%) 1 files
*.ps113 LOC (<1%) 1 files
*.props12 LOC (<1%) 1 files
*.cpp7 LOC (<1%) 1 files
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
gv
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*/[Tt]est/.*".
    • files with paths like ".*/test_.*".
    • files with paths like ".*[.][Tt]est[.].*".
    • files with paths like ".*[.]test[.].*".
    • files with any line of content like ".*/simpletest/.*".
  • 9 files match defined criteria (617 lines of code, 6.2% vs. main code):
    • 8 *.cs files (592 lines of code)
    • 1 *.gv files (25 lines of code)
  • " *.cs" is biggest, containing 95.95% of code.
  • " *.gv" is smallest, containing 4.05% of code.


*.cs592 LOC (95%) 8 files
*.gv25 LOC (4%) 1 files
Generated Code
Automatically generated files, not manually changed after generation.
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]cs" AND any line of content like "[/][/][ ]*".
  • 8 files match defined criteria (1,696 lines of code, 17.0% vs. main code). All matches are in *.cs files.


*.cs1696 LOC (100%) 8 files
Build and Deployment Code
Source code used to configure or support build and deployment process.
csproj
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 ".*[.]csproj".
    • files with paths like ".*[.]bat".
  • 10 files match defined criteria (1,041 lines of code, 10.4% vs. main code):
    • 9 *.csproj files (1,039 lines of code)
    • 1 *.bat files (2 lines of code)
  • " *.csproj" is biggest, containing 99.81% of code.
  • " *.bat" is smallest, containing 0.19% of code.


*.csproj1039 LOC (99%) 9 files
*.bat2 LOC (<1%) 1 files
Other Code
xsd
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 ".*[.]md".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*/LICENSE[.][a-z0-9]+".
    • files with paths like ".*[.](xml|xsd|robot|sql|pgsql|dashboard|profile|ipynb|raml|avsc|al)".
  • 37 files match defined criteria (320 lines of code, 3.2% vs. main code):
    • 30 *.xml files (168 lines of code)
    • 3 *.xsd files (132 lines of code)
    • 4 *.md files (20 lines of code)
  • " *.xml" is biggest, containing 52.5% of code.
  • " *.md" is smallest, containing 6.25% of code.


*.xml168 LOC (52%) 30 files
*.xsd132 LOC (41%) 3 files
*.md20 LOC (6%) 4 files
Analyzers
Info about analyzers used for source code examinations.
  • *.cs files are analyzed with CSharpAnalyzer:
    • 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 namespace heuristics)
  • *.gv 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
  • *.g4 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
  • *.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
  • *.vsixmanifest 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
  • *.vstemplate 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
  • *.ps1 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
  • *.props 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
  • *.cpp 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


2022-01-30 15:05