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 ".*".
381 files match defined criteria (28,660 lines of code, 100.0% vs. main code). All matches are in *.java files.
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 ".*/test/.*".
119 files match defined criteria (7,549 lines of code, 26.3% vs. main code). All matches are in *.java files.
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 ".*/pom[.]xml".
files with paths like ".*[.]sh".
files with paths like ".*/assembly[.]xml".
files with paths like ".*/package[.]json".
7 files match defined criteria (360 lines of code, 1.3% vs. main code). All matches are in *.xml files.
Other Code
The following criteria are used to filter files:
files with paths like ".*[.](md|txt)".
files with paths like ".*[.]md".
files with paths like ".*/resources/(vis_)?templates/.*".
files with paths like ".*/website/.*".
20 files match defined criteria (9,400 lines of code, 32.8% vs. main code):
5 *.txt files (7,197 lines of code)
14 *.html files (2,188 lines of code)
1 *.md files (15 lines of code)
" *.txt" is biggest, containing 76.56% of code.
" *.md" is smallest, containing 0.16% 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)