flutter / platform_tests
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
plist
storyboard
project
properties
  • 16 extensions are included in analyses: plist, xml, gitignore, h, m, md, storyboard, json, gradle, swift, yaml, project, dart, properties, java, bat
  • 3 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (7 files).
    • exclude files with path like ".*/gradle/wrapper/.*" (Gradle) (1 file).
    • exclude files with path like ".*/sokrates_conventions[.]json" (Sokrates scoping conventions) (1 file).
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.

main1085 LOC (57%) 19 files
test0 LOC (0%) 0 files
generated0 LOC (0%) 0 files
build and deployment150 LOC (7%) 4 files
other650 LOC (34%) 25 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 ".*".
  • 19 files match defined criteria (1,085 lines of code, 100.0% vs. main code):
    • 2 *.dart files (388 lines of code)
    • 3 *.swift files (298 lines of code)
    • 5 *.m files (136 lines of code)
    • 1 *.java files (127 lines of code)
    • 3 *.yaml files (119 lines of code)
    • 5 *.h files (17 lines of code)
  • " *.dart" is biggest, containing 35.76% of code.
  • " *.h" is smallest, containing 1.57% of code.


*.dart388 LOC (35%) 2 files
*.swift298 LOC (27%) 3 files
*.m136 LOC (12%) 5 files
*.java127 LOC (11%) 1 files
*.yaml119 LOC (10%) 3 files
*.h17 LOC (1%) 5 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 ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*[.]gradle".
    • files with paths like ".*/AndroidManifest[.]xml".
    • files with paths like ".*[.]bat".
  • 4 files match defined criteria (150 lines of code, 13.8% vs. main code):
    • 3 *.gradle files (84 lines of code)
    • 1 *.bat files (66 lines of code)
  • " *.gradle" is biggest, containing 56% of code.
  • " *.bat" is smallest, containing 44% of code.


*.gradle84 LOC (56%) 3 files
*.bat66 LOC (44%) 1 files
Other Code
plist
storyboard
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 ".*[.]plist".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*[.]storyboard".
    • files with paths like ".*[.]json".
    • files with paths like ".*[.]properties".
    • files with paths like ".*[.](xml|xsd|robot|sql|pgsql|dashboard|profile|ipynb|raml|avsc|al)".
  • 25 files match defined criteria (650 lines of code, 59.9% vs. main code):
    • 3 *.json files (261 lines of code)
    • 6 *.plist files (166 lines of code)
    • 4 *.storyboard files (123 lines of code)
    • 6 *.xml files (69 lines of code)
    • 5 *.md files (27 lines of code)
    • 1 *.properties files (4 lines of code)
  • " *.json" is biggest, containing 40.15% of code.
  • " *.properties" is smallest, containing 0.62% of code.


*.json261 LOC (40%) 3 files
*.plist166 LOC (25%) 6 files
*.storyboard123 LOC (18%) 4 files
*.xml69 LOC (10%) 6 files
*.md27 LOC (4%) 5 files
*.properties4 LOC (<1%) 1 files
Analyzers
Info about analyzers used for source code examinations.
  • *.dart 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
  • *.swift files are analyzed with SwiftAnalyzer:
    • 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
    • No dependency analysis
  • *.m 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
  • *.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)
  • *.yaml files are analyzed with YamlAnalyzer:
    • 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)
    • No unit size analysis
    • No conditional complexity analysis
    • No dependency analysis
  • *.h 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-02-02 22:33