Analysis scope, overview of main, test, generated, deployment, build, and other code.
Source Code Analysis Scope
Files includes and excluded from analyses
- 14 extensions are included in analyses: xml, kt, java, gradle, properties, md, bat, yaml, gitignore, pro, sh, json, yml, txt
- 7 criteria are used to exclude files from analysis:
- exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (49 files).
- exclude files with path like ".*/gradle/wrapper/.*" (Gradle) (25 files).
- exclude files with path like ".*/proguard[-]rules[.]pro" (ProGuard) (8 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).
- The source code folder contains 991 files:
- 853 files are included in analyses.
- 138 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.
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
- The following criteria are used to filter files:
- files with paths like ".*".
- 208 files match defined criteria (11,217 lines of code, 100.0% vs. main code):
- 122 *.kt files (5,740 lines of code)
- 86 *.java files (5,477 lines of code)
- " *.kt" is biggest, containing 51.17% of code.
- " *.java" is smallest, containing 48.83% of code.
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
- The following criteria are used to filter files:
- files with paths like ".*/[Tt]ests/.*".
- files with paths like ".*/src/androidTest/.*".
- files with paths like ".*/[Tt]est/.*".
- files with any line of content like ".*/simpletest/.*".
- 28 files match defined criteria (1,338 lines of code, 11.9% vs. main code):
- 15 *.kt files (694 lines of code)
- 13 *.java files (644 lines of code)
- " *.kt" is biggest, containing 51.87% of code.
- " *.java" is smallest, containing 48.13% of code.
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".
- 103 files match defined criteria (3,175 lines of code, 28.3% vs. main code):
- 25 *.bat files (1,686 lines of code)
- 78 *.gradle files (1,489 lines of code)
- " *.bat" is biggest, containing 53.1% of code.
- " *.gradle" is smallest, containing 46.9% 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 ".*/[.]gitignore".
- files with paths like ".*[.]properties".
- files with paths like ".*[.]json".
- files with paths like ".*/[Ss]amples/.*".
- files with paths like ".*[.]txt".
- files with paths like ".*/[Dd]emos?/.*".
- files with paths like ".*[.](xml|xsd|robot|sql|pgsql|dashboard|profile|ipynb|raml|avsc|al)".
- 514 files match defined criteria (13,605 lines of code, 121.3% vs. main code):
- 450 *.xml files (10,870 lines of code)
- 26 *.md files (1,485 lines of code)
- 14 *.kt files (808 lines of code)
- 23 *.properties files (400 lines of code)
- 1 *.json files (42 lines of code)
- " *.xml" is biggest, containing 79.9% of code.
- " *.json" is smallest, containing 0.31% of code.
Analyzers
Info about analyzers used for source code examinations.
- *.kt files are analyzed with KotlinAnalyzer:
- 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 (based on imports and package statements)
- *.java files are analyzed with JavaAnalyzer:
- 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 package names)
2022-02-03 05:25