dart-lang / test
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
gitattributes
txt
tpl
  • 13 extensions are included in analyses: dart, yaml, md, js, json, css, gitignore, gitattributes, txt, tpl, sh, yml, html
  • 6 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (3 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 ".*/bin/.*" (Binaries for distribution) (1 file).
    • 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.

main90 LOC (<1%) 6 files
test28268 LOC (84%) 246 files
generated0 LOC (0%) 0 files
build and deployment133 LOC (<1%) 1 files
other5063 LOC (15%) 14 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 ".*".
  • 6 files match defined criteria (90 lines of code, 100.0% vs. main code). All matches are in *.yaml files.


*.yaml90 LOC (100%) 6 files
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
tpl
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 ".*/test_.*".
    • files with any line of content like ".*/simpletest/.*".
  • 246 files match defined criteria (28,268 lines of code, 31408.9% vs. main code):
    • 234 *.dart files (27,657 lines of code)
    • 1 *.css files (291 lines of code)
    • 8 *.yaml files (239 lines of code)
    • 1 *.js files (49 lines of code)
    • 1 *.html files (24 lines of code)
    • 1 *.tpl files (8 lines of code)
  • " *.dart" is biggest, containing 97.84% of code.
  • " *.tpl" is smallest, containing 0.03% of code.


*.dart27657 LOC (97%) 234 files
*.css291 LOC (1%) 1 files
*.yaml239 LOC (<1%) 8 files
*.js49 LOC (<1%) 1 files
*.html24 LOC (<1%) 1 files
*.tpl8 LOC (<1%) 1 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 ".*[.]sh".
    • files with paths like ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*/[.]gitattributes".
  • 1 file matches defined criteria (133 lines of code, 147.8% vs. main code). All matches are in *.sh files.


*.sh133 LOC (100%) 1 files
Other Code
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]md".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*[.]json".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*[.]txt".
  • 14 files match defined criteria (5,063 lines of code, 5625.6% vs. main code):
    • 13 *.md files (4,860 lines of code)
    • 1 *.json files (203 lines of code)
  • " *.md" is biggest, containing 95.99% of code.
  • " *.json" is smallest, containing 4.01% of code.


*.md4860 LOC (95%) 13 files
*.json203 LOC (4%) 1 files
Analyzers
Info about analyzers used for source code examinations.
  • *.yaml 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-02-03 02:08