Analysis scope, overview of main, test, generated, deployment, build, and other code.
Source Code Analysis Scope
Files includes and excluded from analyses
- 13 extensions are included in analyses: xml, kt, gradle, json, gitignore, md, yml, properties, pro, txt, bat, sh, yaml
- 7 criteria are used to exclude files from analysis:
- exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (8 files).
- exclude files with path like ".*/proguard[-]rules[.]pro" (ProGuard) (1 file).
- exclude files with path like ".*/gradle/wrapper/.*" (Gradle) (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).
- The source code folder contains 135 files:
- 118 files are included in analyses.
- 17 files are excluded from analyses:
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.
Build and Deployment Code
Source code used to configure or support build and deployment process.
- The following criteria are used to filter files:
- files with paths like ".*[.]gradle".
- files with paths like ".*[.]git[a-z]+".
- files with paths like ".*/[.]gitignore".
- files with paths like ".*/AndroidManifest[.]xml".
- files with paths like ".*[.]bat".
- files with paths like ".*[.]sh".
- 4 files match defined criteria (209 lines of code, ?% vs. main code):
- 3 *.gradle files (148 lines of code)
- 1 *.bat files (61 lines of code)
- " *.gradle" is biggest, containing 70.81% of code.
- " *.bat" is smallest, containing 29.19% of code.
Other Code
- 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 ".*/[Ss]amples/.*".
- files with paths like ".*[.]properties".
- files with paths like ".*[.]txt".
- files with paths like ".*[.](xml|xsd|robot|sql|pgsql|dashboard|profile|ipynb|raml|avsc|al)".
- 114 files match defined criteria (3,210 lines of code, ?% vs. main code):
- 54 *.kt files (1,645 lines of code)
- 57 *.xml files (1,373 lines of code)
- 2 *.md files (162 lines of code)
- 1 *.properties files (30 lines of code)
- " *.kt" is biggest, containing 51.25% of code.
- " *.properties" is smallest, containing 0.93% of code.
Analyzers
Info about analyzers used for source code examinations.
2022-02-03 05:24