Source Code Analysis Scope
Files includes and excluded from analyses
properties

scoping details...
  • 10 extensions are included in analyses: java, groovy, txt, yml, gradle, properties, bat, gitignore, xml, md
  • 7 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/gradle/wrapper/.*" (Gradle) (1 file).
    • exclude files with path like ".*/git[-]commit[-]trailers[.]txt" (Git history trailers) (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) (1 file).
    • exclude files with path like ".*/_sokrates/.*" (Sokrates files) (0 files).
    • exclude files with path like ".*/_sokrates_landscape/.*" (Sokrates landscape files) (0 files).
    • exclude files with path like ".*/sokrates_.*?[.]json" (Sokrates conventions and configurations) (0 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.
main1025 LOC (47%) 18 files
test748 LOC (34%) 8 files
generated0 LOC (0%) 0 files
build and deployment390 LOC (17%) 8 files
other14 LOC (<1%) 3 files
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

java1025 LOC (100%) 18 files

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 18 files match defined criteria (1,025 LOC, 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.
Explore:   circles  |  sunburst

groovy748 LOC (100%) 8 files

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*/[Tt]est/.*".
  • 8 files match defined criteria (748 LOC, 73.0% vs. main code). All matches are in groovy files.
Build and Deployment Code
Source code used to configure or support build and deployment process.
Explore:   circles  |  sunburst

yaml133 LOC (34%) 3 files
xml108 LOC (27%) 1 file
bat71 LOC (18%) 1 file
gitignore58 LOC (14%) 1 file
gradle20 LOC (5%) 2 files

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*/[.]github/workflows/.*[.]ya?ml".
    • files with paths like ".*[.]gradle".
    • files with paths like ".*/checkstyle[.]xml".
    • files with paths like ".*/checkstyle.*".
    • files with paths like ".*[.]bat".
  • 8 files match defined criteria (390 LOC, 38.0% vs. main code):
    • 3 yaml files (133 LOC)
    • 1 xml files (108 LOC)
    • 1 bat files (71 LOC)
    • 1 gitignore files (58 LOC)
    • 2 gradle files (20 LOC)
Other Code
properties
Explore:   circles  |  sunburst

md13 LOC (92%) 2 files
properties1 LOC (7%) 1 file

scope details...
  • 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 ".*[.]properties".
    • files with paths like ".*[.]txt".
  • 3 files match defined criteria (14 LOC, 1.4% vs. main code):
    • 2 md files (13 LOC)
    • 1 properties files (1 LOC)
About This Analysis
learn more about scopes (main, test, generated, build, 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.

learn more about used code analyzers...
  • *.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)