microsoft / mail2bug
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
csproj
txt
cmd
  • 9 extensions are included in analyses: cs, xml, csproj, htm, md, gitignore, txt, json, cmd
  • 5 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (1 file).
    • 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) (0 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.

main3277 LOC (57%) 59 files
test1740 LOC (30%) 14 files
generated0 LOC (0%) 0 files
build and deployment445 LOC (7%) 2 files
other267 LOC (4%) 7 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
cmd
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 59 files match defined criteria (3,277 lines of code, 100.0% vs. main code):
    • 58 *.cs files (3,276 lines of code)
    • 1 *.cmd files (1 lines of code)
  • " *.cs" is biggest, containing 99.97% of code.
  • " *.cmd" is smallest, containing 0.03% of code.


*.cs3276 LOC (99%) 58 files
*.cmd1 LOC (<1%) 1 files
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
csproj
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*/Mocks/.*".
    • files with any line of content like ".*/simpletest/.*".
    • files with paths like ".*UnitTests/.*".
  • 14 files match defined criteria (1,740 lines of code, 53.1% vs. main code):
    • 12 *.cs files (1,533 lines of code)
    • 1 *.csproj files (166 lines of code)
    • 1 *.htm files (41 lines of code)
  • " *.cs" is biggest, containing 88.1% of code.
  • " *.htm" is smallest, containing 2.36% of code.


*.cs1533 LOC (88%) 12 files
*.csproj166 LOC (9%) 1 files
*.htm41 LOC (2%) 1 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 ".*/[.]gitignore".
    • files with paths like ".*[.]csproj".
  • 2 files match defined criteria (445 lines of code, 13.6% vs. main code). All matches are in *.csproj files.


*.csproj445 LOC (100%) 2 files
Other Code
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 ".*/[Dd]ocumentation/.*".
    • files with paths like ".*[.]md".
    • files with paths like ".*/LICENSE[.][a-z0-9]+".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*[.]txt".
    • files with paths like ".*[.](xml|xsd|robot|sql|pgsql|dashboard|profile|ipynb|raml|avsc|al)".
  • 7 files match defined criteria (267 lines of code, 8.1% vs. main code):
    • 4 *.xml files (168 lines of code)
    • 2 *.md files (59 lines of code)
    • 1 *.htm files (40 lines of code)
  • " *.xml" is biggest, containing 62.92% of code.
  • " *.htm" is smallest, containing 14.98% of code.


*.xml168 LOC (62%) 4 files
*.md59 LOC (22%) 2 files
*.htm40 LOC (14%) 1 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)
  • *.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


2022-01-30 09:32