android / location-samples
Source Code Overview

Analysis scope, overview of main, test, generated, deployment, build, and other code.

Source Code Analysis Scope
Files includes and excluded from analyses
properties
pro
txt
  • 14 extensions are included in analyses: xml, gradle, kt, properties, gitignore, java, bat, md, yaml, pro, yml, txt, sh, json
  • 7 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (40 files).
    • exclude files with path like ".*/proguard[-]rules[.]pro" (ProGuard) (11 files).
    • exclude files with path like ".*/gradle/wrapper/.*" (Gradle) (14 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).
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.

main4058 LOC (46%) 53 files
test26 LOC (<1%) 2 files
generated0 LOC (0%) 0 files
build and deployment1575 LOC (18%) 55 files
other3011 LOC (34%) 131 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
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 53 files match defined criteria (4,058 lines of code, 100.0% vs. main code):
    • 22 *.java files (2,230 lines of code)
    • 31 *.kt files (1,828 lines of code)
  • " *.java" is biggest, containing 54.95% of code.
  • " *.kt" is smallest, containing 45.05% of code.


*.java2230 LOC (54%) 22 files
*.kt1828 LOC (45%) 31 files
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
Explore:   circles  |  sunburst
  • 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/.*".
  • 2 files match defined criteria (26 lines of code, 0.6% vs. main code). All matches are in *.kt files.


*.kt26 LOC (100%) 2 files
Build and Deployment Code
Source code used to configure or support build and deployment process.
Explore:   circles  |  sunburst
  • 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".
  • 55 files match defined criteria (1,575 lines of code, 38.8% vs. main code):
    • 14 *.bat files (879 lines of code)
    • 41 *.gradle files (696 lines of code)
  • " *.bat" is biggest, containing 55.81% of code.
  • " *.gradle" is smallest, containing 44.19% of code.


*.bat879 LOC (55%) 14 files
*.gradle696 LOC (44%) 41 files
Other Code
properties
Explore:   circles  |  sunburst
  • 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 ".*[.]properties".
    • files with paths like ".*[.]txt".
    • files with paths like ".*[.](xml|xsd|robot|sql|pgsql|dashboard|profile|ipynb|raml|avsc|al)".
  • 131 files match defined criteria (3,011 lines of code, 74.2% vs. main code):
    • 105 *.xml files (2,325 lines of code)
    • 13 *.md files (476 lines of code)
    • 13 *.properties files (210 lines of code)
  • " *.xml" is biggest, containing 77.22% of code.
  • " *.properties" is smallest, containing 6.97% of code.


*.xml2325 LOC (77%) 105 files
*.md476 LOC (15%) 13 files
*.properties210 LOC (6%) 13 files
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)
  • *.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)


2022-02-03 05:22