Analysis scope, overview of main, test, generated, deployment, build, and other code.
Source Code Analysis Scope
Files includes and excluded from analyses
- 16 extensions are included in analyses: java, xml, gradle, sh, pro, md, txt, json, mk, properties, cpp, gitignore, ps1, bat, yml, gitmodules
- 7 criteria are used to exclude files from analysis:
- exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (6 files).
- exclude files with path like ".*/proguard[-]rules[.]pro" (ProGuard) (7 files).
- 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) (2 files).
- The source code folder contains 489 files:
- 469 files are included in analyses.
- 20 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 ".*".
- 210 files match defined criteria (18,355 lines of code, 100.0% vs. main code):
- 208 *.java files (18,068 lines of code)
- 1 *.ps1 files (201 lines of code)
- 1 *.cpp files (86 lines of code)
- " *.java" is biggest, containing 98.44% of code.
- " *.cpp" is smallest, containing 0.47% 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 ".*/src/androidTest/.*".
- files with paths like ".*/[Tt]est/.*".
- files with any line of content like ".*/simpletest/.*".
- 168 files match defined criteria (27,581 lines of code, 150.3% vs. main code):
- 167 *.java files (27,572 lines of code)
- 1 *.gradle files (9 lines of code)
- " *.java" is biggest, containing 99.97% of code.
- " *.gradle" is smallest, containing 0.03% 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 ".*[.]git[a-z]+".
- files with paths like ".*/[.]gitignore".
- files with paths like ".*/[.]gitmodules".
- files with paths like ".*[.]sh".
- files with paths like ".*[.]gradle".
- files with paths like ".*[.]mk".
- files with paths like ".*/AndroidManifest[.]xml".
- files with paths like ".*[.]bat".
- 23 files match defined criteria (691 lines of code, 3.8% vs. main code):
- 12 *.gradle files (439 lines of code)
- 8 *.sh files (178 lines of code)
- 1 *.bat files (61 lines of code)
- 2 *.mk files (13 lines of code)
- " *.gradle" is biggest, containing 63.53% of code.
- " *.mk" is smallest, containing 1.88% of code.
Other Code
- The following criteria are used to filter files:
- files with paths like ".*[.]json".
- files with paths like ".*[.]md".
- files with paths like ".*/[.]gitignore".
- files with paths like ".*/README[.][a-z0-9]+".
- files with paths like ".*[.]txt".
- files with paths like ".*[.]properties".
- files with paths like ".*[.](xml|xsd|robot|sql|pgsql|dashboard|profile|ipynb|raml|avsc|al)".
- 68 files match defined criteria (2,388 lines of code, 13.0% vs. main code):
- 63 *.xml files (1,716 lines of code)
- 3 *.md files (548 lines of code)
- 1 *.json files (123 lines of code)
- 1 *.properties files (1 lines of code)
- " *.xml" is biggest, containing 71.86% of code.
- " *.properties" is smallest, containing 0.04% of code.
Analyzers
Info about analyzers used for source code examinations.
- *.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)
- *.ps1 files are analyzed with DefaultLanguageAnalyzer:
- All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
- Basic code cleaning (empty lines removed for LOC calculations and duplication calculations)
- No unit size analysis
- No conditional complexity analysis
- No dependency analysis
- *.cpp files are analyzed with CppAnalyzer:
- 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
2022-01-30 13:42