azure / perf-tests - 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

proto

txt

mod

editorconfig

gitattributes

patch

cfg

22 extensions are included in analyses: go, yaml, md, proto, s, sh, gitignore, txt, py, mod, json, js, sql, editorconfig, c, toml, bash, css, gitattributes, patch, html, cfg
7 criteria are used to exclude files from analysis:

exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (33 files).
exclude files with path like ".*/Chart\.js" (Chart.js) (1 file).
exclude files with path like ".*/angular([^.]*)\.js" (AngularJS) (1 file).
exclude files with path like ".*/testdata/.*" (Test data) (16 files).
exclude files with path like ".*/docs/.*" (Documentation) (9 files).
exclude files with path like ".*/[Vv]endors?/.*" (Dependencies) (3137 files).
exclude files with path like ".*/(3rd|[Tt]hird)[-_]?[Pp]arty/.*" (Dependencies) (0 files).

The source code folder contains 4,109 files:

659 files are included in analyses.
3,450 files are excluded from analyses:

Explore all 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.

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 ".*".

524 files match defined criteria (58,712 LOC, 100.0% vs. main code):

284 *.yaml files (30,436 LOC)
219 *.go files (25,763 LOC)
15 *.py files (2,071 LOC)
1 *.js files (295 LOC)
1 *.html files (69 LOC)
1 *.css files (45 LOC)
3 *.sql files (33 LOC)

" *.yaml" is biggest, containing 51.84% of LOC.
" *.sql" is smallest, containing 0.06% of LOC.

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 ".*_test[.].*".
files with paths like ".*/[Tt]est/.*".
files with paths like ".*[-]tests/.*".
files with paths like ".*/test_.*".
files with paths like ".*[-]test[-].*".
files with paths like ".*/test[.].*".
files with paths like ".*/test[-]data/.*".

48 files match defined criteria (6,701 LOC, 11.4% vs. main code):

37 *.go files (6,296 LOC)
8 *.yaml files (243 LOC)
2 *.py files (144 LOC)
1 *.sh files (18 LOC)

" *.go" is biggest, containing 93.96% of LOC.
" *.sh" is smallest, containing 0.27% of LOC.

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 ".*[.]sh".
files with paths like ".*/[.]gitattributes".

16 files match defined criteria (435 LOC, 0.7% vs. main code). All matches are in *.sh files.

Other Code

mod

txt

patch

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 ".*/[.]gitignore".
files with paths like ".*/go[.]mod".
files with paths like ".*/[Ee]xamples/.*".
files with paths like ".*[.]json".
files with paths like ".*[.]txt".
files with paths like ".*[.]patch".
files with paths like ".*/vendor/.*".
files with paths like ".*/LICENSE[.][a-z0-9]+".
files with paths like ".*[.]editorconfig".

71 files match defined criteria (17,209 LOC, 29.3% vs. main code):

5 *.json files (14,361 LOC)
31 *.md files (1,370 LOC)
15 *.mod files (752 LOC)
17 *.txt files (586 LOC)
2 *.yaml files (75 LOC)
1 *.patch files (65 LOC)

" *.json" is biggest, containing 83.45% of LOC.
" *.patch" is smallest, containing 0.38% of LOC.

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

*.go files are analyzed with GoLangAnalyzer:

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

Basic heuristic dependency analysis

*.py files are analyzed with PythonAnalyzer:

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

Basic heuristic 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

*.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

*.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

*.sql files are analyzed with SqlAnalyzer:

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

2025-05-06 23:18