microsoft / skype-interviews-docs
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
gitattributes
dockerignore
txt
  • 13 extensions are included in analyses: md, cs, json, yml, csproj, svg, gitignore, js, gitattributes, dockerignore, ps1, txt, php
  • 5 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (5 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) (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.

main3 LOC (<1%) 1 files
test0 LOC (0%) 0 files
generated136 LOC (7%) 1 files
build and deployment0 LOC (0%) 0 files
other1691 LOC (92%) 30 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 ".*".
  • 1 file matches defined criteria (3 lines of code, 100.0% vs. main code). All matches are in *.yml files.


*.yml3 LOC (100%) 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 ".*/package[-]lock[.]json".
  • 1 file matches defined criteria (136 lines of code, 4533.3% vs. main code). All matches are in *.json files.


*.json136 LOC (100%) 1 files
Other Code
csproj
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 ".*/README[.][a-z0-9]+".
    • files with paths like ".*/[Ss]amples/.*".
    • files with paths like ".*/[.]dockerignore".
    • files with paths like ".*[.]txt".
  • 30 files match defined criteria (1,691 lines of code, 56366.7% vs. main code):
    • 15 *.md files (1,052 lines of code)
    • 6 *.cs files (261 lines of code)
    • 3 *.json files (202 lines of code)
    • 2 *.csproj files (82 lines of code)
    • 1 *.php files (49 lines of code)
    • 1 *.js files (25 lines of code)
    • 2 *.yml files (20 lines of code)
  • " *.md" is biggest, containing 62.21% of code.
  • " *.yml" is smallest, containing 1.18% of code.


*.md1052 LOC (62%) 15 files
*.cs261 LOC (15%) 6 files
*.json202 LOC (11%) 3 files
*.csproj82 LOC (4%) 2 files
*.php49 LOC (2%) 1 files
*.js25 LOC (1%) 1 files
*.yml20 LOC (1%) 2 files
Analyzers
Info about analyzers used for source code examinations.
  • *.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 16:05